OpenCloudOS-Kernel/Documentation/ABI
Linus Torvalds 30813656c6 dmaengine fixes for v6.5
- HAS_IOMEM fixes for fsl edma and intel idma
 - Return value fix, interrupt vector setting and typo fix for xilinx xdma
 - Email updates for codeaurora email domain move
 - correct pause status for pl330 driver
 - idxd clear flag on disable fix
 - function documentation fix for owl dma
 - potential un-allocated memory fix for mcf driver
 -----BEGIN PGP SIGNATURE-----
 
 iQIzBAABCAAdFiEE+vs47OPLdNbVcHzyfBQHDyUjg0cFAmTUlVgACgkQfBQHDyUj
 g0eEQw/8DQbcN/+5S8wGKNgD6rxJmKFHfhkegQerT2/jvr9G++Pz/nyAMre3QBHI
 DHJnsr+1enupdtYuCZRu91sDpSTP85JKgorRmHs8YizLyqGG1VU4a6X0q0d2Ghwk
 5QZSfCEvogVeoilubfMgyTIkn+uOD6Hygqc8+HyAouX29gPNfd23KN4aaLPAL+Di
 wFvQVYKoOiDmKqcanaDfqUtyy13hV5ZOF33loqFmKaFEMfH40Pn7ZAnpIB/IrPaY
 WEGUSJvLSRN9GdprdxqHkhOJ8XLCNEDA62x4LHoO/Lnd21V1XfkWtYRPsM7fgSDV
 Pw5Lhk2/DIqBBfif83C0/9kUrCbe9fd+J5zBnN4lHFGbmccy/oefH80McErCLxtd
 hvxauI6BT4v53OQg1F9MrNrmwvyGwYTTY+0M4L6iAlZvW08ZQ+8N5YHTV3dvc7Qd
 8CTHHWwnlT0UP6KTRqtTGiEkk20I6VaVVd/S1AKPfCXECLi72bbgEct+Ud8bRlX5
 kTobnVYpcVZub6OJDZxlTLjuV57Kh5wAYq6ny/FVR//+6KHyd+hB/yjaRqChM+mv
 ew2n/081Sx3RspB94RT+J5LvPnBR0si6Rdm5GpASyOw54iWkhL22KF4MTTjWvUW6
 VyudlCno7e9Fn2WNm1eXblxZhV4F20nSmdBnLmxPGZKMrQdbYMQ=
 =oNNL
 -----END PGP SIGNATURE-----

Merge tag 'dmaengine-fix-6.5' of git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/dmaengine

Pull dmaengine fixes from Vinod Koul:

 - HAS_IOMEM fixes for fsl edma and intel idma

 - return-value fix, interrupt vector setting and typo fix for xilinx
   xdma

 - email updates for codeaurora email domain move

 - correct pause status for pl330 driver

 - idxd clear flag on disable fix

 - function documentation fix for owl dma

 - potential un-allocated memory fix for mcf driver

* tag 'dmaengine-fix-6.5' of git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/dmaengine:
  dmaengine: xilinx: xdma: Fix typo
  dmaengine: xilinx: xdma: Fix interrupt vector setting
  dmaengine: owl-dma: Modify mismatched function name
  dmaengine: idxd: Clear PRS disable flag when disabling IDXD device
  dmaengine: pl330: Return DMA_PAUSED when transaction is paused
  dmaengine: qcom_hidma: Update codeaurora email domain
  dmaengine: mcf-edma: Fix a potential un-allocated memory access
  dmaengine: xilinx: xdma: Fix Judgment of the return value
  idmaengine: make FSL_EDMA and INTEL_IDMA64 depends on HAS_IOMEM
2023-08-10 11:32:26 -07:00
..
obsolete docs: update ocfs2-devel mailing list address 2023-07-08 09:29:29 -07:00
removed docs: update ocfs2-devel mailing list address 2023-07-08 09:29:29 -07:00
stable docs: update ocfs2-devel mailing list address 2023-07-08 09:29:29 -07:00
testing dmaengine fixes for v6.5 2023-08-10 11:32:26 -07:00
README docs: ABI: README: specify that files should be ReST compatible 2020-10-30 13:07:01 +01:00

README

This directory attempts to document the ABI between the Linux kernel and
userspace, and the relative stability of these interfaces.  Due to the
everchanging nature of Linux, and the differing maturity levels, these
interfaces should be used by userspace programs in different ways.

We have four different levels of ABI stability, as shown by the four
different subdirectories in this location.  Interfaces may change levels
of stability according to the rules described below.

The different levels of stability are:

  stable/
	This directory documents the interfaces that the developer has
	defined to be stable.  Userspace programs are free to use these
	interfaces with no restrictions, and backward compatibility for
	them will be guaranteed for at least 2 years.  Most interfaces
	(like syscalls) are expected to never change and always be
	available.

  testing/
	This directory documents interfaces that are felt to be stable,
	as the main development of this interface has been completed.
	The interface can be changed to add new features, but the
	current interface will not break by doing this, unless grave
	errors or security problems are found in them.  Userspace
	programs can start to rely on these interfaces, but they must be
	aware of changes that can occur before these interfaces move to
	be marked stable.  Programs that use these interfaces are
	strongly encouraged to add their name to the description of
	these interfaces, so that the kernel developers can easily
	notify them if any changes occur (see the description of the
	layout of the files below for details on how to do this.)

  obsolete/
	This directory documents interfaces that are still remaining in
	the kernel, but are marked to be removed at some later point in
	time.  The description of the interface will document the reason
	why it is obsolete and when it can be expected to be removed.

  removed/
	This directory contains a list of the old interfaces that have
	been removed from the kernel.

Every file in these directories will contain the following information:

What:		Short description of the interface
Date:		Date created
KernelVersion:	Kernel version this feature first showed up in.
Contact:	Primary contact for this interface (may be a mailing list)
Description:	Long description of the interface and how to use it.
Users:		All users of this interface who wish to be notified when
		it changes.  This is very important for interfaces in
		the "testing" stage, so that kernel developers can work
		with userspace developers to ensure that things do not
		break in ways that are unacceptable.  It is also
		important to get feedback for these interfaces to make
		sure they are working in a proper way and do not need to
		be changed further.


Note:
   The fields should be use a simple notation, compatible with ReST markup.
   Also, the file **should not** have a top-level index, like::

	===
	foo
	===

How things move between levels:

Interfaces in stable may move to obsolete, as long as the proper
notification is given.

Interfaces may be removed from obsolete and the kernel as long as the
documented amount of time has gone by.

Interfaces in the testing state can move to the stable state when the
developers feel they are finished.  They cannot be removed from the
kernel tree without going through the obsolete state first.

It's up to the developer to place their interfaces in the category they
wish for it to start out in.


Notable bits of non-ABI, which should not under any circumstances be considered
stable:

- Kconfig.  Userspace should not rely on the presence or absence of any
  particular Kconfig symbol, in /proc/config.gz, in the copy of .config
  commonly installed to /boot, or in any invocation of the kernel build
  process.

- Kernel-internal symbols.  Do not rely on the presence, absence, location, or
  type of any kernel symbol, either in System.map files or the kernel binary
  itself.  See Documentation/process/stable-api-nonsense.rst.