Unverified Commit b8f3b564 authored by Mark Brown's avatar Mark Brown
Browse files

Merge tag 'v5.15-rc6' into asoc-5.16 

Linux 5.15-rc6
parents 4e52cb9e 519d8195

CREDITS

+1 −0
Original line number Diff line number Diff line
@@ -971,6 +971,7 @@ D: PowerPC 
N: Daniel Drake

E: dsd@gentoo.org

D: USBAT02 CompactFlash support in usb-storage

D: ZD1211RW wireless driver

S: UK



N: Oleg Drokin

Documentation/admin-guide/README.rst

+1 −1
Original line number Diff line number Diff line
@@ -259,7 +259,7 @@ Configuring the kernel 
Compiling the kernel

--------------------



 - Make sure you have at least gcc 4.9 available.

 - Make sure you have at least gcc 5.1 available.

   For more information, refer to :ref:`Documentation/process/changes.rst <changes>`.



   Please note that you can still run a.out user programs with this kernel.

Documentation/admin-guide/cgroup-v2.rst

+14 −14
Original line number Diff line number Diff line
@@ -1226,7 +1226,7 @@ PAGE_SIZE multiple when read back. 


	Note that all fields in this file are hierarchical and the

	file modified event can be generated due to an event down the

	hierarchy. For for the local events at the cgroup level see

	hierarchy. For the local events at the cgroup level see

	memory.events.local.



	  low
@@ -2170,19 +2170,19 @@ existing device files. 


Cgroup v2 device controller has no interface files and is implemented

on top of cgroup BPF. To control access to device files, a user may

create bpf programs of the BPF_CGROUP_DEVICE type and attach them

to cgroups. On an attempt to access a device file, corresponding

BPF programs will be executed, and depending on the return value

the attempt will succeed or fail with -EPERM.



A BPF_CGROUP_DEVICE program takes a pointer to the bpf_cgroup_dev_ctx

structure, which describes the device access attempt: access type

(mknod/read/write) and device (type, major and minor numbers).

If the program returns 0, the attempt fails with -EPERM, otherwise

it succeeds.



An example of BPF_CGROUP_DEVICE program may be found in the kernel

source tree in the tools/testing/selftests/bpf/progs/dev_cgroup.c file.

create bpf programs of type BPF_PROG_TYPE_CGROUP_DEVICE and attach

them to cgroups with BPF_CGROUP_DEVICE flag. On an attempt to access a

device file, corresponding BPF programs will be executed, and depending

on the return value the attempt will succeed or fail with -EPERM.



A BPF_PROG_TYPE_CGROUP_DEVICE program takes a pointer to the

bpf_cgroup_dev_ctx structure, which describes the device access attempt:

access type (mknod/read/write) and device (type, major and minor numbers).

If the program returns 0, the attempt fails with -EPERM, otherwise it

succeeds.



An example of BPF_PROG_TYPE_CGROUP_DEVICE program may be found in

tools/testing/selftests/bpf/progs/dev_cgroup.c in the kernel source tree.





RDMA

Documentation/admin-guide/kernel-parameters.txt

+1 −1
Original line number Diff line number Diff line
@@ -1266,7 +1266,7 @@ 
			The VGA and EFI output is eventually overwritten by

			the real console.



			The xen output can only be used by Xen PV guests.

			The xen option can only be used in Xen domains.



			The sclp output can only be used on s390.

Documentation/core-api/irq/irq-domain.rst

+3 −2
Original line number Diff line number Diff line
@@ -175,9 +175,10 @@ for IRQ numbers that are passed to struct device registrations. In that 
case the Linux IRQ numbers cannot be dynamically assigned and the legacy

mapping should be used.



As the name implies, the *_legacy() functions are deprecated and only

As the name implies, the \*_legacy() functions are deprecated and only

exist to ease the support of ancient platforms. No new users should be

added.

added. Same goes for the \*_simple() functions when their use results

in the legacy behaviour.



The legacy map assumes a contiguous range of IRQ numbers has already

been allocated for the controller and that the IRQ number can be