Merge drm/drm-next into drm-intel-next (83970cd6) · Commits · EulixOS / Software / Kernel

.mailmap

+5 −0

Original line number	Diff line number	Diff line
		@@ -71,6 +71,7 @@ Boris Brezillon <bbrezillon@kernel.org> <boris.brezillon@free-electrons.com>
		Brian Avery <b.avery@hp.com>
		Brian King <brking@us.ibm.com>
		Brian Silverman <bsilver16384@gmail.com> <brian.silverman@bluerivertech.com>
		Cai Huoqing <cai.huoqing@linux.dev> <caihuoqing@baidu.com>
		Changbin Du <changbin.du@intel.com> <changbin.du@gmail.com>
		Changbin Du <changbin.du@intel.com> <changbin.du@intel.com>
		Chao Yu <chao@kernel.org> <chao2.yu@samsung.com>
		@@ -187,6 +188,8 @@ Jiri Slaby <jirislaby@kernel.org> <jslaby@novell.com>
		Jiri Slaby <jirislaby@kernel.org> <jslaby@suse.com>
		Jiri Slaby <jirislaby@kernel.org> <jslaby@suse.cz>
		Jiri Slaby <jirislaby@kernel.org> <xslaby@fi.muni.cz>
		Jisheng Zhang <jszhang@kernel.org> <jszhang@marvell.com>
		Jisheng Zhang <jszhang@kernel.org> <Jisheng.Zhang@synaptics.com>
		Johan Hovold <johan@kernel.org> <jhovold@gmail.com>
		Johan Hovold <johan@kernel.org> <johan@hovoldconsulting.com>
		John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
		@@ -210,12 +213,14 @@ Kees Cook <keescook@chromium.org> <kees@ubuntu.com>
		Keith Busch <kbusch@kernel.org> <keith.busch@intel.com>
		Keith Busch <kbusch@kernel.org> <keith.busch@linux.intel.com>
		Kenneth W Chen <kenneth.w.chen@intel.com>
		Kirill Tkhai <kirill.tkhai@openvz.org> <ktkhai@virtuozzo.com>
		Konstantin Khlebnikov <koct9i@gmail.com> <khlebnikov@yandex-team.ru>
		Konstantin Khlebnikov <koct9i@gmail.com> <k.khlebnikov@samsung.com>
		Koushik <raghavendra.koushik@neterion.com>
		Krishna Manikandan <quic_mkrishn@quicinc.com> <mkrishn@codeaurora.org>
		Krzysztof Kozlowski <krzk@kernel.org> <k.kozlowski.k@gmail.com>
		Krzysztof Kozlowski <krzk@kernel.org> <k.kozlowski@samsung.com>
		Krzysztof Kozlowski <krzk@kernel.org> <krzysztof.kozlowski@canonical.com>
		Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
		Kuogee Hsieh <quic_khsieh@quicinc.com> <khsieh@codeaurora.org>
		Leonardo Bras <leobras.c@gmail.com> <leonardo@linux.ibm.com>

CREDITS

+6 −0

Original line number	Diff line number	Diff line
		@@ -895,6 +895,12 @@ S: 3000 FORE Drive
		S: Warrendale, Pennsylvania 15086
		S: USA

		N: Ludovic Desroches
		E: ludovic.desroches@microchip.com
		D: Maintainer for ARM/Microchip (AT91) SoC support
		D: Author of ADC, pinctrl, XDMA and SDHCI drivers for this platform
		S: France

		N: Martin Devera
		E: devik@cdi.cz
		W: http://luxik.cdi.cz/~devik/qos/

Documentation/ABI/obsolete/procfs-i8k

0 → 100644

+10 −0

Original line number	Diff line number	Diff line
		What: /proc/i8k
		Date: November 2001
		KernelVersion: 2.4.14
		Contact: Pali Rohár <pali@kernel.org>
		Description: Legacy interface for getting/setting sensor information like
		fan speed, temperature, serial number, hotkey status etc
		on Dell Laptops.
		Since the driver is now using the standard hwmon sysfs interface,
		the procfs interface is deprecated.
		Users: https://github.com/vitorafsr/i8kutils

Documentation/ABI/removed/sysfs-mce

0 → 100644

+37 −0

Original line number	Diff line number	Diff line
		What: /sys/devices/system/machinecheck/machinecheckX/tolerant
		Contact: Borislav Petkov <bp@suse.de>
		Date: Dec, 2021
		Description:
		Unused and obsolete after the advent of recoverable machine
		checks (see last sentence below) and those are present since
		2010 (Nehalem).

		Original description:

		The entries appear for each CPU, but they are truly shared
		between all CPUs.

		Tolerance level. When a machine check exception occurs for a
		non corrected machine check the kernel can take different
		actions.

		Since machine check exceptions can happen any time it is
		sometimes risky for the kernel to kill a process because it
		defies normal kernel locking rules. The tolerance level
		configures how hard the kernel tries to recover even at some
		risk of deadlock. Higher tolerant values trade potentially
		better uptime with the risk of a crash or even corruption
		(for tolerant >= 3).

		== ===========================================================
		0 always panic on uncorrected errors, log corrected errors
		1 panic or SIGBUS on uncorrected errors, log corrected errors
		2 SIGBUS or log uncorrected errors, log corrected errors
		3 never panic or SIGBUS, log all errors (for testing only)
		== ===========================================================

		Default: 1

		Note this only makes a difference if the CPU allows recovery
		from a machine check exception. Current x86 CPUs generally
		do not.

Documentation/ABI/stable/sysfs-block

+49 −0

Original line number	Diff line number	Diff line
		@@ -155,6 +155,55 @@ Description:
		last zone of the device which may be smaller.


		What: /sys/block/<disk>/queue/crypto/
		Date: February 2022
		Contact: linux-block@vger.kernel.org
		Description:
		The presence of this subdirectory of /sys/block/<disk>/queue/
		indicates that the device supports inline encryption. This
		subdirectory contains files which describe the inline encryption
		capabilities of the device. For more information about inline
		encryption, refer to Documentation/block/inline-encryption.rst.


		What: /sys/block/<disk>/queue/crypto/max_dun_bits
		Date: February 2022
		Contact: linux-block@vger.kernel.org
		Description:
		[RO] This file shows the maximum length, in bits, of data unit
		numbers accepted by the device in inline encryption requests.


		What: /sys/block/<disk>/queue/crypto/modes/<mode>
		Date: February 2022
		Contact: linux-block@vger.kernel.org
		Description:
		[RO] For each crypto mode (i.e., encryption/decryption
		algorithm) the device supports with inline encryption, a file
		will exist at this location. It will contain a hexadecimal
		number that is a bitmask of the supported data unit sizes, in
		bytes, for that crypto mode.

		Currently, the crypto modes that may be supported are:

		* AES-256-XTS
		* AES-128-CBC-ESSIV
		* Adiantum

		For example, if a device supports AES-256-XTS inline encryption
		with data unit sizes of 512 and 4096 bytes, the file
		/sys/block/<disk>/queue/crypto/modes/AES-256-XTS will exist and
		will contain "0x1200".


		What: /sys/block/<disk>/queue/crypto/num_keyslots
		Date: February 2022
		Contact: linux-block@vger.kernel.org
		Description:
		[RO] This file shows the number of keyslots the device has for
		use with inline encryption.


		What: /sys/block/<disk>/queue/dax
		Date: June 2016
		Contact: linux-block@vger.kernel.org