docs: fix broken documentation links
Mostly due to x86 and acpi conversion, several documentation links are still pointing to the old file. Fix them. Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org> Reviewed-by: Wolfram Sang <wsa@the-dreams.de> Reviewed-by: Sven Van Asbroeck <TheSven73@gmail.com> Reviewed-by: Bhupesh Sharma <bhsharma@redhat.com> Acked-by: Mark Brown <broonie@kernel.org> Signed-off-by: Jonathan Corbet <corbet@lwn.net>alistair/sunxi64-5.4-dsi
Mauro Carvalho Chehab
Jonathan Corbet
parent
1eecbcdca2
commit
cb1aaebea8
|
|
@ -96,4 +96,4 @@ where
|
|||
<URL:http://www.uefi.org/sites/default/files/resources/_DSD-hierarchical-data-extension-UUID-v1.1.pdf>,
|
||||
referenced 2019-02-21.
|
||||
|
||||
[7] Documentation/acpi/dsd/data-node-reference.txt
|
||||
[7] Documentation/firmware-guide/acpi/dsd/data-node-references.rst
|
||||
|
|
|
|||
|
|
@ -167,7 +167,7 @@ parameter is applicable::
|
|||
X86-32 X86-32, aka i386 architecture is enabled.
|
||||
X86-64 X86-64 architecture is enabled.
|
||||
More X86-64 boot options can be found in
|
||||
Documentation/x86/x86_64/boot-options.txt .
|
||||
Documentation/x86/x86_64/boot-options.rst.
|
||||
X86 Either 32-bit or 64-bit x86 (same as X86-32+X86-64)
|
||||
X86_UV SGI UV support is enabled.
|
||||
XEN Xen support is enabled
|
||||
|
|
@ -181,10 +181,10 @@ In addition, the following text indicates that the option::
|
|||
Parameters denoted with BOOT are actually interpreted by the boot
|
||||
loader, and have no meaning to the kernel directly.
|
||||
Do not modify the syntax of boot loader parameters without extreme
|
||||
need or coordination with <Documentation/x86/boot.txt>.
|
||||
need or coordination with <Documentation/x86/boot.rst>.
|
||||
|
||||
There are also arch-specific kernel-parameters not documented here.
|
||||
See for example <Documentation/x86/x86_64/boot-options.txt>.
|
||||
See for example <Documentation/x86/x86_64/boot-options.rst>.
|
||||
|
||||
Note that ALL kernel parameters listed below are CASE SENSITIVE, and that
|
||||
a trailing = on the name of any parameter states that that parameter will
|
||||
|
|
|
|||
|
|
@ -53,7 +53,7 @@
|
|||
ACPI_DEBUG_PRINT statements, e.g.,
|
||||
ACPI_DEBUG_PRINT((ACPI_DB_INFO, ...
|
||||
The debug_level mask defaults to "info". See
|
||||
Documentation/acpi/debug.txt for more information about
|
||||
Documentation/firmware-guide/acpi/debug.rst for more information about
|
||||
debug layers and levels.
|
||||
|
||||
Enable processor driver info messages:
|
||||
|
|
@ -963,7 +963,7 @@
|
|||
for details.
|
||||
|
||||
nompx [X86] Disables Intel Memory Protection Extensions.
|
||||
See Documentation/x86/intel_mpx.txt for more
|
||||
See Documentation/x86/intel_mpx.rst for more
|
||||
information about the feature.
|
||||
|
||||
nopku [X86] Disable Memory Protection Keys CPU feature found
|
||||
|
|
@ -1189,7 +1189,7 @@
|
|||
that is to be dynamically loaded by Linux. If there are
|
||||
multiple variables with the same name but with different
|
||||
vendor GUIDs, all of them will be loaded. See
|
||||
Documentation/acpi/ssdt-overlays.txt for details.
|
||||
Documentation/admin-guide/acpi/ssdt-overlays.rst for details.
|
||||
|
||||
|
||||
eisa_irq_edge= [PARISC,HW]
|
||||
|
|
@ -2383,7 +2383,7 @@
|
|||
|
||||
mce [X86-32] Machine Check Exception
|
||||
|
||||
mce=option [X86-64] See Documentation/x86/x86_64/boot-options.txt
|
||||
mce=option [X86-64] See Documentation/x86/x86_64/boot-options.rst
|
||||
|
||||
md= [HW] RAID subsystems devices and level
|
||||
See Documentation/admin-guide/md.rst.
|
||||
|
|
@ -2439,7 +2439,7 @@
|
|||
set according to the
|
||||
CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE kernel config
|
||||
option.
|
||||
See Documentation/memory-hotplug.txt.
|
||||
See Documentation/admin-guide/mm/memory-hotplug.rst.
|
||||
|
||||
memmap=exactmap [KNL,X86] Enable setting of an exact
|
||||
E820 memory map, as specified by the user.
|
||||
|
|
@ -2528,7 +2528,7 @@
|
|||
mem_encrypt=on: Activate SME
|
||||
mem_encrypt=off: Do not activate SME
|
||||
|
||||
Refer to Documentation/x86/amd-memory-encryption.txt
|
||||
Refer to Documentation/virtual/kvm/amd-memory-encryption.rst
|
||||
for details on when memory encryption can be activated.
|
||||
|
||||
mem_sleep_default= [SUSPEND] Default system suspend mode:
|
||||
|
|
@ -3529,7 +3529,7 @@
|
|||
See Documentation/blockdev/paride.txt.
|
||||
|
||||
pirq= [SMP,APIC] Manual mp-table setup
|
||||
See Documentation/x86/i386/IO-APIC.txt.
|
||||
See Documentation/x86/i386/IO-APIC.rst.
|
||||
|
||||
plip= [PPT,NET] Parallel port network link
|
||||
Format: { parport<nr> | timid | 0 }
|
||||
|
|
@ -5055,7 +5055,7 @@
|
|||
Can be used multiple times for multiple devices.
|
||||
|
||||
vga= [BOOT,X86-32] Select a particular video mode
|
||||
See Documentation/x86/boot.txt and
|
||||
See Documentation/x86/boot.rst and
|
||||
Documentation/svga.txt.
|
||||
Use vga=ask for menu.
|
||||
This is actually a boot loader parameter; the value is
|
||||
|
|
|
|||
|
|
@ -199,7 +199,7 @@ Architecture (MCA)\ [#f3]_.
|
|||
mode).
|
||||
|
||||
.. [#f3] For more details about the Machine Check Architecture (MCA),
|
||||
please read Documentation/x86/x86_64/machinecheck at the Kernel tree.
|
||||
please read Documentation/x86/x86_64/machinecheck.rst at the Kernel tree.
|
||||
|
||||
EDAC - Error Detection And Correction
|
||||
*************************************
|
||||
|
|
|
|||
|
|
@ -16,8 +16,8 @@ Required properties:
|
|||
In this case, the ENETC node should include a "mdio" sub-node
|
||||
that in turn should contain the "ethernet-phy" node describing the
|
||||
external phy. Below properties are required, their bindings
|
||||
already defined in ethernet.txt or phy.txt, under
|
||||
Documentation/devicetree/bindings/net/*.
|
||||
already defined in Documentation/devicetree/bindings/net/ethernet.txt or
|
||||
Documentation/devicetree/bindings/net/phy.txt.
|
||||
|
||||
Required:
|
||||
|
||||
|
|
@ -51,8 +51,7 @@ Example:
|
|||
connection:
|
||||
|
||||
In this case, the ENETC port node defines a fixed link connection,
|
||||
as specified by "fixed-link.txt", under
|
||||
Documentation/devicetree/bindings/net/*.
|
||||
as specified by Documentation/devicetree/bindings/net/fixed-link.txt.
|
||||
|
||||
Required:
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ Amlogic Meson AXG DWC PCIE SoC controller
|
|||
Amlogic Meson PCIe host controller is based on the Synopsys DesignWare PCI core.
|
||||
It shares common functions with the PCIe DesignWare core driver and
|
||||
inherits common properties defined in
|
||||
Documentation/devicetree/bindings/pci/designware-pci.txt.
|
||||
Documentation/devicetree/bindings/pci/designware-pcie.txt.
|
||||
|
||||
Additional properties are described here:
|
||||
|
||||
|
|
|
|||
|
|
@ -97,7 +97,7 @@ Second Level Nodes - Regulators
|
|||
sent for this regulator including those which are for a
|
||||
strictly lower power state.
|
||||
|
||||
Other properties defined in Documentation/devicetree/bindings/regulator.txt
|
||||
Other properties defined in Documentation/devicetree/bindings/regulator/regulator.txt
|
||||
may also be used. regulator-initial-mode and regulator-allowed-modes may be
|
||||
specified for VRM regulators using mode values from
|
||||
include/dt-bindings/regulator/qcom,rpmh-regulator.h. regulator-allow-bypass
|
||||
|
|
|
|||
|
|
@ -277,7 +277,7 @@ it with special cases.
|
|||
the decompressor (the real mode entry point goes to the same 32bit
|
||||
entry point once it switched into protected mode). That entry point
|
||||
supports one calling convention which is documented in
|
||||
Documentation/x86/boot.txt
|
||||
Documentation/x86/boot.rst
|
||||
The physical pointer to the device-tree block (defined in chapter II)
|
||||
is passed via setup_data which requires at least boot protocol 2.09.
|
||||
The type filed is defined as
|
||||
|
|
|
|||
|
|
@ -101,7 +101,7 @@ with the help of _DSD (Device Specific Data), introduced in ACPI 5.1::
|
|||
}
|
||||
|
||||
For more information about the ACPI GPIO bindings see
|
||||
Documentation/acpi/gpio-properties.txt.
|
||||
Documentation/firmware-guide/acpi/gpio-properties.rst.
|
||||
|
||||
Platform Data
|
||||
-------------
|
||||
|
|
|
|||
|
|
@ -437,7 +437,7 @@ case, it will be handled by the GPIO subsystem automatically. However, if the
|
|||
_DSD is not present, the mappings between GpioIo()/GpioInt() resources and GPIO
|
||||
connection IDs need to be provided by device drivers.
|
||||
|
||||
For details refer to Documentation/acpi/gpio-properties.txt
|
||||
For details refer to Documentation/firmware-guide/acpi/gpio-properties.rst
|
||||
|
||||
|
||||
Interacting With the Legacy GPIO Subsystem
|
||||
|
|
|
|||
|
|
@ -339,7 +339,7 @@ a code like this::
|
|||
There are also devm_* versions of these functions which release the
|
||||
descriptors once the device is released.
|
||||
|
||||
See Documentation/acpi/gpio-properties.txt for more information about the
|
||||
See Documentation/firmware-guide/acpi/gpio-properties.rst for more information about the
|
||||
_DSD binding related to GPIOs.
|
||||
|
||||
MFD devices
|
||||
|
|
|
|||
|
|
@ -68,7 +68,7 @@ c. Filter out the debug layer/level matched logs when the specified
|
|||
|
||||
Where:
|
||||
0xXXXXXXXX/0xYYYYYYYY
|
||||
Refer to Documentation/acpi/debug.txt for possible debug layer/level
|
||||
Refer to Documentation/firmware-guide/acpi/debug.rst for possible debug layer/level
|
||||
masking values.
|
||||
\PPPP.AAAA.TTTT.HHHH
|
||||
Full path of a control method that can be found in the ACPI namespace.
|
||||
|
|
|
|||
|
|
@ -85,7 +85,7 @@ Method 1c: Declare the I2C devices via ACPI
|
|||
-------------------------------------------
|
||||
|
||||
ACPI can also describe I2C devices. There is special documentation for this
|
||||
which is currently located at Documentation/acpi/enumeration.txt.
|
||||
which is currently located at Documentation/firmware-guide/acpi/enumeration.rst.
|
||||
|
||||
|
||||
Method 2: Instantiate the devices explicitly
|
||||
|
|
|
|||
|
|
@ -155,7 +155,7 @@ is 0x15 and the full version number is 0x234, this file will contain
|
|||
the value 340 = 0x154.
|
||||
|
||||
See the type_of_loader and ext_loader_type fields in
|
||||
Documentation/x86/boot.txt for additional information.
|
||||
Documentation/x86/boot.rst for additional information.
|
||||
|
||||
==============================================================
|
||||
|
||||
|
|
@ -167,7 +167,7 @@ The complete bootloader version number. In the example above, this
|
|||
file will contain the value 564 = 0x234.
|
||||
|
||||
See the type_of_loader and ext_loader_ver fields in
|
||||
Documentation/x86/boot.txt for additional information.
|
||||
Documentation/x86/boot.rst for additional information.
|
||||
|
||||
==============================================================
|
||||
|
||||
|
|
|
|||
|
|
@ -241,7 +241,7 @@ scripts/coccinelle目录下已经打包了相当多的内核“语义补丁”
|
|||
|
||||
任何添加新用户空间界面的代码（包括新的sysfs或/proc文件）都应该包含该界面的
|
||||
文档，该文档使用户空间开发人员能够知道他们在使用什么。请参阅
|
||||
Documentation/abi/readme，了解如何格式化此文档以及需要提供哪些信息。
|
||||
Documentation/ABI/README，了解如何格式化此文档以及需要提供哪些信息。
|
||||
|
||||
文件 :ref:`Documentation/admin-guide/kernel-parameters.rst <kernelparameters>`
|
||||
描述了内核的所有引导时间参数。任何添加新参数的补丁都应该向该文件添加适当的
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ physical address space. This "ought to be enough for anybody" ©.
|
|||
QEMU 2.9 and later support 5-level paging.
|
||||
|
||||
Virtual memory layout for 5-level paging is described in
|
||||
Documentation/x86/x86_64/mm.txt
|
||||
Documentation/x86/x86_64/mm.rst
|
||||
|
||||
|
||||
Enabling 5-level paging
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ only the AMD64 specific ones are listed here.
|
|||
|
||||
Machine check
|
||||
=============
|
||||
Please see Documentation/x86/x86_64/machinecheck for sysfs runtime tunables.
|
||||
Please see Documentation/x86/x86_64/machinecheck.rst for sysfs runtime tunables.
|
||||
|
||||
mce=off
|
||||
Disable machine check
|
||||
|
|
@ -89,7 +89,7 @@ APICs
|
|||
Don't use the local APIC (alias for i386 compatibility)
|
||||
|
||||
pirq=...
|
||||
See Documentation/x86/i386/IO-APIC.txt
|
||||
See Documentation/x86/i386/IO-APIC.rst
|
||||
|
||||
noapictimer
|
||||
Don't set up the APIC timer
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ For more information on the features of cpusets, see
|
|||
Documentation/cgroup-v1/cpusets.txt.
|
||||
There are a number of different configurations you can use for your needs. For
|
||||
more information on the numa=fake command line option and its various ways of
|
||||
configuring fake nodes, see Documentation/x86/x86_64/boot-options.txt.
|
||||
configuring fake nodes, see Documentation/x86/x86_64/boot-options.rst.
|
||||
|
||||
For the purposes of this introduction, we'll assume a very primitive NUMA
|
||||
emulation setup of "numa=fake=4*512,". This will split our system memory into
|
||||
|
|
|
|||
|
|
@ -3874,7 +3874,7 @@ F: Documentation/devicetree/bindings/hwmon/cirrus,lochnagar.txt
|
|||
F: Documentation/devicetree/bindings/pinctrl/cirrus,lochnagar.txt
|
||||
F: Documentation/devicetree/bindings/regulator/cirrus,lochnagar.txt
|
||||
F: Documentation/devicetree/bindings/sound/cirrus,lochnagar.txt
|
||||
F: Documentation/hwmon/lochnagar
|
||||
F: Documentation/hwmon/lochnagar.rst
|
||||
|
||||
CISCO FCOE HBA DRIVER
|
||||
M: Satish Kharat <satishkh@cisco.com>
|
||||
|
|
@ -11272,7 +11272,7 @@ NXP FXAS21002C DRIVER
|
|||
M: Rui Miguel Silva <rmfrfs@gmail.com>
|
||||
L: linux-iio@vger.kernel.org
|
||||
S: Maintained
|
||||
F: Documentation/devicetree/bindings/iio/gyroscope/fxas21002c.txt
|
||||
F: Documentation/devicetree/bindings/iio/gyroscope/nxp,fxas21002c.txt
|
||||
F: drivers/iio/gyro/fxas21002c_core.c
|
||||
F: drivers/iio/gyro/fxas21002c.h
|
||||
F: drivers/iio/gyro/fxas21002c_i2c.c
|
||||
|
|
|
|||
|
|
@ -1263,7 +1263,7 @@ config SMP
|
|||
uniprocessor machines. On a uniprocessor machine, the kernel
|
||||
will run faster if you say N here.
|
||||
|
||||
See also <file:Documentation/x86/i386/IO-APIC.txt>,
|
||||
See also <file:Documentation/x86/i386/IO-APIC.rst>,
|
||||
<file:Documentation/lockup-watchdogs.txt> and the SMP-HOWTO available at
|
||||
<http://tldp.org/HOWTO/SMP-HOWTO.html>.
|
||||
|
||||
|
|
|
|||
|
|
@ -53,7 +53,7 @@ static void *image_load(struct kimage *image,
|
|||
|
||||
/*
|
||||
* We require a kernel with an unambiguous Image header. Per
|
||||
* Documentation/booting.txt, this is the case when image_size
|
||||
* Documentation/arm64/booting.txt, this is the case when image_size
|
||||
* is non-zero (practically speaking, since v3.17).
|
||||
*/
|
||||
h = (struct arm64_image_header *)kernel;
|
||||
|
|
|
|||
|
|
@ -395,7 +395,7 @@ config SMP
|
|||
Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
|
||||
Management" code will be disabled if you say Y here.
|
||||
|
||||
See also <file:Documentation/x86/i386/IO-APIC.txt>,
|
||||
See also <file:Documentation/x86/i386/IO-APIC.rst>,
|
||||
<file:Documentation/lockup-watchdogs.txt> and the SMP-HOWTO available at
|
||||
<http://www.tldp.org/docs.html#howto>.
|
||||
|
||||
|
|
@ -1290,7 +1290,7 @@ config MICROCODE
|
|||
the Linux kernel.
|
||||
|
||||
The preferred method to load microcode from a detached initrd is described
|
||||
in Documentation/x86/microcode.txt. For that you need to enable
|
||||
in Documentation/x86/microcode.rst. For that you need to enable
|
||||
CONFIG_BLK_DEV_INITRD in order for the loader to be able to scan the
|
||||
initrd for microcode blobs.
|
||||
|
||||
|
|
@ -1329,7 +1329,7 @@ config MICROCODE_OLD_INTERFACE
|
|||
It is inadequate because it runs too late to be able to properly
|
||||
load microcode on a machine and it needs special tools. Instead, you
|
||||
should've switched to the early loading method with the initrd or
|
||||
builtin microcode by now: Documentation/x86/microcode.txt
|
||||
builtin microcode by now: Documentation/x86/microcode.rst
|
||||
|
||||
config X86_MSR
|
||||
tristate "/dev/cpu/*/msr - Model-specific register support"
|
||||
|
|
@ -1478,7 +1478,7 @@ config X86_5LEVEL
|
|||
A kernel with the option enabled can be booted on machines that
|
||||
support 4- or 5-level paging.
|
||||
|
||||
See Documentation/x86/x86_64/5level-paging.txt for more
|
||||
See Documentation/x86/x86_64/5level-paging.rst for more
|
||||
information.
|
||||
|
||||
Say N if unsure.
|
||||
|
|
@ -1626,7 +1626,7 @@ config ARCH_MEMORY_PROBE
|
|||
depends on X86_64 && MEMORY_HOTPLUG
|
||||
help
|
||||
This option enables a sysfs memory/probe interface for testing.
|
||||
See Documentation/memory-hotplug.txt for more information.
|
||||
See Documentation/admin-guide/mm/memory-hotplug.rst for more information.
|
||||
If you are unsure how to answer this question, answer N.
|
||||
|
||||
config ARCH_PROC_KCORE_TEXT
|
||||
|
|
@ -1783,7 +1783,7 @@ config MTRR
|
|||
You can safely say Y even if your machine doesn't have MTRRs, you'll
|
||||
just add about 9 KB to your kernel.
|
||||
|
||||
See <file:Documentation/x86/mtrr.txt> for more information.
|
||||
See <file:Documentation/x86/mtrr.rst> for more information.
|
||||
|
||||
config MTRR_SANITIZER
|
||||
def_bool y
|
||||
|
|
@ -1895,7 +1895,7 @@ config X86_INTEL_MPX
|
|||
process and adds some branches to paths used during
|
||||
exec() and munmap().
|
||||
|
||||
For details, see Documentation/x86/intel_mpx.txt
|
||||
For details, see Documentation/x86/intel_mpx.rst
|
||||
|
||||
If unsure, say N.
|
||||
|
||||
|
|
|
|||
|
|
@ -156,7 +156,7 @@ config IOMMU_DEBUG
|
|||
code. When you use it make sure you have a big enough
|
||||
IOMMU/AGP aperture. Most of the options enabled by this can
|
||||
be set more finegrained using the iommu= command line
|
||||
options. See Documentation/x86/x86_64/boot-options.txt for more
|
||||
options. See Documentation/x86/x86_64/boot-options.rst for more
|
||||
details.
|
||||
|
||||
config IOMMU_LEAK
|
||||
|
|
|
|||
|
|
@ -313,7 +313,7 @@ start_sys_seg: .word SYSSEG # obsolete and meaningless, but just
|
|||
|
||||
type_of_loader: .byte 0 # 0 means ancient bootloader, newer
|
||||
# bootloaders know to change this.
|
||||
# See Documentation/x86/boot.txt for
|
||||
# See Documentation/x86/boot.rst for
|
||||
# assigned ids
|
||||
|
||||
# flags, unused bits must be zero (RFU) bit within loadflags
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@
|
|||
*
|
||||
* entry.S contains the system-call and fault low-level handling routines.
|
||||
*
|
||||
* Some of this is documented in Documentation/x86/entry_64.txt
|
||||
* Some of this is documented in Documentation/x86/entry_64.rst
|
||||
*
|
||||
* A note on terminology:
|
||||
* - iret frame: Architecture defined interrupt frame from SS to RIP
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ static void sanitize_boot_params(struct boot_params *boot_params)
|
|||
* IMPORTANT NOTE TO BOOTLOADER AUTHORS: do not simply clear
|
||||
* this field. The purpose of this field is to guarantee
|
||||
* compliance with the x86 boot spec located in
|
||||
* Documentation/x86/boot.txt . That spec says that the
|
||||
* Documentation/x86/boot.rst . That spec says that the
|
||||
* *whole* structure should be cleared, after which only the
|
||||
* portion defined by struct setup_header (boot_params->hdr)
|
||||
* should be copied in.
|
||||
|
|
|
|||
|
|
@ -48,7 +48,7 @@
|
|||
|
||||
#define __START_KERNEL_map _AC(0xffffffff80000000, UL)
|
||||
|
||||
/* See Documentation/x86/x86_64/mm.txt for a description of the memory map. */
|
||||
/* See Documentation/x86/x86_64/mm.rst for a description of the memory map. */
|
||||
|
||||
#define __PHYSICAL_MASK_SHIFT 52
|
||||
|
||||
|
|
|
|||
|
|
@ -103,7 +103,7 @@ extern unsigned int ptrs_per_p4d;
|
|||
#define PGDIR_MASK (~(PGDIR_SIZE - 1))
|
||||
|
||||
/*
|
||||
* See Documentation/x86/x86_64/mm.txt for a description of the memory map.
|
||||
* See Documentation/x86/x86_64/mm.rst for a description of the memory map.
|
||||
*
|
||||
* Be very careful vs. KASLR when changing anything here. The KASLR address
|
||||
* range must not overlap with anything except the KASAN shadow area, which
|
||||
|
|
|
|||
|
|
@ -61,7 +61,7 @@ static u8 amd_ucode_patch[PATCH_MAX_SIZE];
|
|||
|
||||
/*
|
||||
* Microcode patch container file is prepended to the initrd in cpio
|
||||
* format. See Documentation/x86/microcode.txt
|
||||
* format. See Documentation/x86/microcode.rst
|
||||
*/
|
||||
static const char
|
||||
ucode_path[] __maybe_unused = "kernel/x86/microcode/AuthenticAMD.bin";
|
||||
|
|
|
|||
|
|
@ -416,7 +416,7 @@ static void *bzImage64_load(struct kimage *image, char *kernel,
|
|||
efi_map_offset = params_cmdline_sz;
|
||||
efi_setup_data_offset = efi_map_offset + ALIGN(efi_map_sz, 16);
|
||||
|
||||
/* Copy setup header onto bootparams. Documentation/x86/boot.txt */
|
||||
/* Copy setup header onto bootparams. Documentation/x86/boot.rst */
|
||||
setup_header_size = 0x0202 + kernel[0x0201] - setup_hdr_offset;
|
||||
|
||||
/* Is there a limit on setup header size? */
|
||||
|
|
|
|||
|
|
@ -70,7 +70,7 @@ void __init pci_iommu_alloc(void)
|
|||
}
|
||||
|
||||
/*
|
||||
* See <Documentation/x86/x86_64/boot-options.txt> for the iommu kernel
|
||||
* See <Documentation/x86/x86_64/boot-options.rst> for the iommu kernel
|
||||
* parameter documentation.
|
||||
*/
|
||||
static __init int iommu_setup(char *p)
|
||||
|
|
|
|||
|
|
@ -711,7 +711,7 @@ void native_flush_tlb_others(const struct cpumask *cpumask,
|
|||
}
|
||||
|
||||
/*
|
||||
* See Documentation/x86/tlb.txt for details. We choose 33
|
||||
* See Documentation/x86/tlb.rst for details. We choose 33
|
||||
* because it is large enough to cover the vast majority (at
|
||||
* least 95%) of allocations, and is small enough that we are
|
||||
* confident it will not cause too much overhead. Each single
|
||||
|
|
|
|||
|
|
@ -86,7 +86,7 @@ static void __init init_pvh_bootparams(bool xen_guest)
|
|||
}
|
||||
|
||||
/*
|
||||
* See Documentation/x86/boot.txt.
|
||||
* See Documentation/x86/boot.rst.
|
||||
*
|
||||
* Version 2.12 supports Xen entry point but we will use default x86/PC
|
||||
* environment (i.e. hardware_subarch 0).
|
||||
|
|
|
|||
|
|
@ -333,7 +333,7 @@ config ACPI_CUSTOM_DSDT_FILE
|
|||
depends on !STANDALONE
|
||||
help
|
||||
This option supports a custom DSDT by linking it into the kernel.
|
||||
See Documentation/acpi/dsdt-override.txt
|
||||
See Documentation/admin-guide/acpi/dsdt-override.rst
|
||||
|
||||
Enter the full path name to the file which includes the AmlCode
|
||||
or dsdt_aml_code declaration.
|
||||
|
|
@ -355,7 +355,7 @@ config ACPI_TABLE_UPGRADE
|
|||
This option provides functionality to upgrade arbitrary ACPI tables
|
||||
via initrd. No functional change if no ACPI tables are passed via
|
||||
initrd, therefore it's safe to say Y.
|
||||
See Documentation/acpi/initrd_table_override.txt for details
|
||||
See Documentation/admin-guide/acpi/initrd_table_override.rst for details
|
||||
|
||||
config ACPI_TABLE_OVERRIDE_VIA_BUILTIN_INITRD
|
||||
bool "Override ACPI tables from built-in initrd"
|
||||
|
|
@ -365,7 +365,7 @@ config ACPI_TABLE_OVERRIDE_VIA_BUILTIN_INITRD
|
|||
This option provides functionality to override arbitrary ACPI tables
|
||||
from built-in uncompressed initrd.
|
||||
|
||||
See Documentation/acpi/initrd_table_override.txt for details
|
||||
See Documentation/admin-guide/acpi/initrd_table_override.rst for details
|
||||
|
||||
config ACPI_DEBUG
|
||||
bool "Debug Statements"
|
||||
|
|
@ -374,7 +374,7 @@ config ACPI_DEBUG
|
|||
output and increases the kernel size by around 50K.
|
||||
|
||||
Use the acpi.debug_layer and acpi.debug_level kernel command-line
|
||||
parameters documented in Documentation/acpi/debug.txt and
|
||||
parameters documented in Documentation/firmware-guide/acpi/debug.rst and
|
||||
Documentation/admin-guide/kernel-parameters.rst to control the type and
|
||||
amount of debug output.
|
||||
|
||||
|
|
@ -445,7 +445,7 @@ config ACPI_CUSTOM_METHOD
|
|||
help
|
||||
This debug facility allows ACPI AML methods to be inserted and/or
|
||||
replaced without rebooting the system. For details refer to:
|
||||
Documentation/acpi/method-customizing.txt.
|
||||
Documentation/firmware-guide/acpi/method-customizing.rst.
|
||||
|
||||
NOTE: This option is security sensitive, because it allows arbitrary
|
||||
kernel memory to be written to by root (uid=0) users, allowing them
|
||||
|
|
|
|||
|
|
@ -1075,7 +1075,7 @@ static int ftgmac100_mii_probe(struct ftgmac100 *priv, phy_interface_t intf)
|
|||
}
|
||||
|
||||
/* Indicate that we support PAUSE frames (see comment in
|
||||
* Documentation/networking/phy.txt)
|
||||
* Documentation/networking/phy.rst)
|
||||
*/
|
||||
phy_support_asym_pause(phydev);
|
||||
|
||||
|
|
|
|||
|
|
@ -54,8 +54,8 @@ a limited few common behaviours and properties. This allows us to define
|
|||
a simple interface consisting of a character device and a set of sysfs files:
|
||||
|
||||
See:
|
||||
Documentation/ABI/testing/sysfs-class-fieldbus-dev
|
||||
Documentation/ABI/testing/fieldbus-dev-cdev
|
||||
drivers/staging/fieldbus/Documentation/ABI/sysfs-class-fieldbus-dev
|
||||
drivers/staging/fieldbus/Documentation/ABI/fieldbus-dev-cdev
|
||||
|
||||
Note that this simple interface does not provide a way to modify adapter
|
||||
configuration settings. It is therefore useful only for adapters that get their
|
||||
|
|
|
|||
|
|
@ -1694,7 +1694,7 @@ EXPORT_SYMBOL_GPL(vhost_dev_ioctl);
|
|||
|
||||
/* TODO: This is really inefficient. We need something like get_user()
|
||||
* (instruction directly accesses the data, with an exception table entry
|
||||
* returning -EFAULT). See Documentation/x86/exception-tables.txt.
|
||||
* returning -EFAULT). See Documentation/x86/exception-tables.rst.
|
||||
*/
|
||||
static int set_bit_to_user(int nr, void __user *addr)
|
||||
{
|
||||
|
|
|
|||
|
|
@ -25,7 +25,7 @@
|
|||
#define ACPI_MAX_STRING 80
|
||||
|
||||
/*
|
||||
* Please update drivers/acpi/debug.c and Documentation/acpi/debug.txt
|
||||
* Please update drivers/acpi/debug.c and Documentation/firmware-guide/acpi/debug.rst
|
||||
* if you add to this list.
|
||||
*/
|
||||
#define ACPI_BUS_COMPONENT 0x00010000
|
||||
|
|
|
|||
|
|
@ -85,7 +85,7 @@ struct fs_parameter {
|
|||
* Superblock creation fills in ->root whereas reconfiguration begins with this
|
||||
* already set.
|
||||
*
|
||||
* See Documentation/filesystems/mounting.txt
|
||||
* See Documentation/filesystems/mount_api.txt
|
||||
*/
|
||||
struct fs_context {
|
||||
const struct fs_context_operations *ops;
|
||||
|
|
|
|||
|
|
@ -77,7 +77,7 @@
|
|||
* state. This is called immediately after commit_creds().
|
||||
*
|
||||
* Security hooks for mount using fs_context.
|
||||
* [See also Documentation/filesystems/mounting.txt]
|
||||
* [See also Documentation/filesystems/mount_api.txt]
|
||||
*
|
||||
* @fs_context_dup:
|
||||
* Allocate and attach a security structure to sc->security. This pointer
|
||||
|
|
|
|||
|
|
@ -165,7 +165,7 @@ config MEMORY_HOTPLUG_DEFAULT_ONLINE
|
|||
onlining policy (/sys/devices/system/memory/auto_online_blocks) which
|
||||
determines what happens to newly added memory regions. Policy setting
|
||||
can always be changed at runtime.
|
||||
See Documentation/memory-hotplug.txt for more information.
|
||||
See Documentation/admin-guide/mm/memory-hotplug.rst for more information.
|
||||
|
||||
Say Y here if you want all hot-plugged memory blocks to appear in
|
||||
'online' state by default.
|
||||
|
|
|
|||
|
|
@ -62,7 +62,7 @@ config PAGE_TABLE_ISOLATION
|
|||
ensuring that the majority of kernel addresses are not mapped
|
||||
into userspace.
|
||||
|
||||
See Documentation/x86/pti.txt for more details.
|
||||
See Documentation/x86/pti.rst for more details.
|
||||
|
||||
config SECURITY_INFINIBAND
|
||||
bool "Infiniband Security Hooks"
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@
|
|||
* Userspace note:
|
||||
* The same principle works for userspace, because 'error' pointers
|
||||
* fall down to the unused hole far from user space, as described
|
||||
* in Documentation/x86/x86_64/mm.txt for x86_64 arch:
|
||||
* in Documentation/x86/x86_64/mm.rst for x86_64 arch:
|
||||
*
|
||||
* 0000000000000000 - 00007fffffffffff (=47 bits) user space, different per mm hole caused by [48:63] sign extension
|
||||
* ffffffffffe00000 - ffffffffffffffff (=2 MB) unused hole
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ instructions). Similarly, it knows how to follow switch statements, for
|
|||
which gcc sometimes uses jump tables.
|
||||
|
||||
(Objtool also has an 'orc generate' subcommand which generates debuginfo
|
||||
for the ORC unwinder. See Documentation/x86/orc-unwinder.txt in the
|
||||
for the ORC unwinder. See Documentation/x86/orc-unwinder.rst in the
|
||||
kernel tree for more details.)
|
||||
|
||||
|
||||
|
|
@ -101,7 +101,7 @@ b) ORC (Oops Rewind Capability) unwind table generation
|
|||
band. So it doesn't affect runtime performance and it can be
|
||||
reliable even when interrupts or exceptions are involved.
|
||||
|
||||
For more details, see Documentation/x86/orc-unwinder.txt.
|
||||
For more details, see Documentation/x86/orc-unwinder.rst.
|
||||
|
||||
c) Higher live patching compatibility rate
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue