Merge tag 'docs-5.9-2' of git://git.lwn.net/linux

# This list is used by git-shortlog to fix a few botched name translations

# in the git archive, either because the author's full name was messed up

# and/or not always written the same way, making contributions from the

# same person appearing not to be so or badly displayed.

# same person appearing not to be so or badly displayed. Also allows for

# old email addresses to map to new email addresses.

#

# For format details, see "MAPPING AUTHORS" in "man git-shortlog".

#

# Please keep this list dictionary sorted.

#

# This comment is parsed by git-shortlog:

# repo-abbrev: /pub/scm/linux/kernel/git/

#

Aaron Durbin <adurbin@google.com>

Adam Oldham <oldhamca@gmail.com>

Adam Radford <aradford@gmail.com>

			memory region [offset, offset + size] for that kernel

			image. If '@offset' is omitted, then a suitable offset

			is selected automatically.

			[KNL, x86_64] select a region under 4G first, and

			[KNL, X86-64] Select a region under 4G first, and

			fall back to reserve region above 4G when '@offset'

			hasn't been specified.

			See Documentation/admin-guide/kdump/kdump.rst for further details.

			Documentation/admin-guide/kdump/kdump.rst for an example.

	crashkernel=size[KMG],high

			[KNL, x86_64] range could be above 4G. Allow kernel

			[KNL, X86-64] range could be above 4G. Allow kernel

			to allocate physical memory region from top, so could

			be above 4G if system have more than 4G ram installed.

			Otherwise memory region will be allocated below 4G, if

			available.

			It will be ignored if crashkernel=X is specified.

	crashkernel=size[KMG],low

			[KNL, x86_64] range under 4G. When crashkernel=X,high

			[KNL, X86-64] range under 4G. When crashkernel=X,high

			is passed, kernel could allocate physical memory region

			above 4G, that cause second kernel crash on system

			that require some amount of low memory, e.g. swiotlb

	gamma=		[HW,DRM]

	gart_fix_e820=	[X86_64] disable the fix e820 for K8 GART

	gart_fix_e820=	[X86-64] disable the fix e820 for K8 GART

			Format: off | on

			default: on

			Format: 0 | 1

			Default set by CONFIG_INIT_ON_FREE_DEFAULT_ON.

	init_pkru=	[x86] Specify the default memory protection keys rights

	init_pkru=	[X86] Specify the default memory protection keys rights

			register contents for all processes.  0x55555554 by

			default (disallow access to all but pkey 0).  Can

			override in debugfs after boot.

	inport.irq=	[HW] Inport (ATI XL and Microsoft) busmouse driver

			Format: <irq>

	int_pln_enable	[x86] Enable power limit notification interrupt

	int_pln_enable	[X86] Enable power limit notification interrupt

	integrity_audit=[IMA]

			Format: { "0" | "1" }

			bypassed by not enabling DMAR with this option. In

			this case, gfx device will use physical address for

			DMA.

		forcedac [x86_64]

		forcedac [X86-64]

			With this option iommu will not optimize to look

			for io virtual address below 32-bit forcing dual

			address cycle on pci bus for cards supporting greater

		strict	regions from userspace.

		relaxed

	iommu=		[x86]

	iommu=		[X86]

		off

		force

		noforce

		merge

		nomerge

		soft

		pt		[x86]

		nopt		[x86]

		pt		[X86]

		nopt		[X86]

		nobypass	[PPC/POWERNV]

			Disable IOMMU bypass, using IOMMU for PCI devices.

	iucv=		[HW,NET]

	ivrs_ioapic	[HW,X86_64]

	ivrs_ioapic	[HW,X86-64]

			Provide an override to the IOAPIC-ID<->DEVICE-ID

			mapping provided in the IVRS ACPI table. For

			example, to map IOAPIC-ID decimal 10 to

			PCI device 00:14.0 write the parameter as:

				ivrs_ioapic[10]=00:14.0

	ivrs_hpet	[HW,X86_64]

	ivrs_hpet	[HW,X86-64]

			Provide an override to the HPET-ID<->DEVICE-ID

			mapping provided in the IVRS ACPI table. For

			example, to map HPET-ID decimal 0 to

			PCI device 00:14.0 write the parameter as:

				ivrs_hpet[0]=00:14.0

	ivrs_acpihid	[HW,X86_64]

	ivrs_acpihid	[HW,X86-64]

			Provide an override to the ACPI-HID:UID<->DEVICE-ID

			mapping provided in the IVRS ACPI table. For

			example, to map UART-HID:UID AMD0020:0 to

	lapic		[X86-32,APIC] Enable the local APIC even if BIOS

			disabled it.

	lapic=		[x86,APIC] "notscdeadline" Do not use TSC deadline

	lapic=		[X86,APIC] "notscdeadline" Do not use TSC deadline

			value for LAPIC timer one-shot implementation. Default

			back to the programmable timer unit in the LAPIC.

			register save and restore. The kernel will only save

			legacy floating-point registers on task switch.

	nohugeiomap	[KNL,x86,PPC] Disable kernel huge I/O mappings.

	nohugeiomap	[KNL,X86,PPC] Disable kernel huge I/O mappings.

	nosmt		[KNL,S390] Disable symmetric multithreading (SMT).

			Equivalent to smt=1.

			[KNL,x86] Disable symmetric multithreading (SMT).

			[KNL,X86] Disable symmetric multithreading (SMT).

			nosmt=force: Force disable SMT, cannot be undone

				     via the sysfs control file.

	pt.		[PARIDE]

			See Documentation/admin-guide/blockdev/paride.rst.

	pti=		[X86_64] Control Page Table Isolation of user and

	pti=		[X86-64] Control Page Table Isolation of user and

			kernel address spaces.  Disabling this feature

			removes hardening, but improves performance of

			system calls and interrupts.

			Not specifying this option is equivalent to pti=auto.

	nopti		[X86_64]

	nopti		[X86-64]

			Equivalent to pti=off

	pty.legacy_count=

	CDC_DRIVE_STATUS	/* driver implements drive status */

The capability flag is declared *const*, to prevent drivers from

accidentally tampering with the contents. The capability fags actually

accidentally tampering with the contents. The capability flags actually

inform `cdrom.c` of what the driver can do. If the drive found

by the driver does not have the capability, is can be masked out by

the *cdrom_device_info* variable *mask*. For instance, the SCSI CD-ROM

Only a few routines in `cdrom.c` are exported to the drivers. In this

new section we will discuss these, as well as the functions that `take

over' the CD-ROM interface to the kernel. The header file belonging

over` the CD-ROM interface to the kernel. The header file belonging

to `cdrom.c` is called `cdrom.h`. Formerly, some of the contents of this

file were placed in the file `ucdrom.h`, but this file has now been

merged back into `cdrom.h`.

IDR usage

=========

Start by initialising an IDR, either with :c:func:`DEFINE_IDR`

for statically allocated IDRs or :c:func:`idr_init` for dynamically

Start by initialising an IDR, either with DEFINE_IDR()

for statically allocated IDRs or idr_init() for dynamically

allocated IDRs.

You can call :c:func:`idr_alloc` to allocate an unused ID.  Look up

the pointer you associated with the ID by calling :c:func:`idr_find`

and free the ID by calling :c:func:`idr_remove`.

You can call idr_alloc() to allocate an unused ID.  Look up

the pointer you associated with the ID by calling idr_find()

and free the ID by calling idr_remove().

If you need to change the pointer associated with an ID, you can call

:c:func:`idr_replace`.  One common reason to do this is to reserve an

idr_replace().  One common reason to do this is to reserve an

ID by passing a ``NULL`` pointer to the allocation function; initialise the

object with the reserved ID and finally insert the initialised object

into the IDR.

Some users need to allocate IDs larger than ``INT_MAX``.  So far all of

these users have been content with a ``UINT_MAX`` limit, and they use

:c:func:`idr_alloc_u32`.  If you need IDs that will not fit in a u32,

idr_alloc_u32().  If you need IDs that will not fit in a u32,

we will work with you to address your needs.

If you need to allocate IDs sequentially, you can use

:c:func:`idr_alloc_cyclic`.  The IDR becomes less efficient when dealing

idr_alloc_cyclic().  The IDR becomes less efficient when dealing

with larger IDs, so using this function comes at a slight cost.

To perform an action on all pointers used by the IDR, you can

either use the callback-based :c:func:`idr_for_each` or the

iterator-style :c:func:`idr_for_each_entry`.  You may need to use

:c:func:`idr_for_each_entry_continue` to continue an iteration.  You can

also use :c:func:`idr_get_next` if the iterator doesn't fit your needs.

either use the callback-based idr_for_each() or the

iterator-style idr_for_each_entry().  You may need to use

idr_for_each_entry_continue() to continue an iteration.  You can

also use idr_get_next() if the iterator doesn't fit your needs.

When you have finished using an IDR, you can call :c:func:`idr_destroy`

When you have finished using an IDR, you can call idr_destroy()

to release the memory used by the IDR.  This will not free the objects

pointed to from the IDR; if you want to do that, use one of the iterators

to do it.

You can use :c:func:`idr_is_empty` to find out whether there are any

You can use idr_is_empty() to find out whether there are any

IDs currently allocated.

If you need to take a lock while allocating a new ID from the IDR,

you may need to pass a restrictive set of GFP flags, which can lead

to the IDR being unable to allocate memory.  To work around this,

you can call :c:func:`idr_preload` before taking the lock, and then

:c:func:`idr_preload_end` after the allocation.

you can call idr_preload() before taking the lock, and then

idr_preload_end() after the allocation.

.. kernel-doc:: include/linux/idr.h

   :doc: idr sync

    make coccicheck M=drivers/net/wireless/

To apply Coccinelle on a file basis, instead of a directory basis, the

following command may be used::

C variable is used by the makefile to select which files to work with.

This variable can be used to run scripts for the entire kernel, a

specific directory, or for a single file.

    make C=1 CHECK="scripts/coccicheck"

For example, to check drivers/bluetooth/bfusb.c, the value 1 is

passed to the C variable to check files that make considers

need to be compiled.::

To check only newly edited code, use the value 2 for the C flag, i.e.::

    make C=1 CHECK=scripts/coccicheck drivers/bluetooth/bfusb.o

    make C=2 CHECK="scripts/coccicheck"

The value 2 is passed to the C variable to check files regardless of

whether they need to be compiled or not.::

    make C=2 CHECK=scripts/coccicheck drivers/bluetooth/bfusb.o

In these modes, which work on a file basis, there is no information

about semantic patches displayed, and no commit message proposed.