Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux

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>

authored by

Mauro Carvalho Chehab and committed by
Jonathan Corbet
cb1aaebe 1eecbcdc

+70 -71
+1 -1
Documentation/acpi/dsd/leds.txt
··· 96 96 <URL:http://www.uefi.org/sites/default/files/resources/_DSD-hierarchical-data-extension-UUID-v1.1.pdf>, 97 97 referenced 2019-02-21. 98 98 99 - [7] Documentation/acpi/dsd/data-node-reference.txt 99 + [7] Documentation/firmware-guide/acpi/dsd/data-node-references.rst
+3 -3
Documentation/admin-guide/kernel-parameters.rst
··· 167 167 X86-32 X86-32, aka i386 architecture is enabled. 168 168 X86-64 X86-64 architecture is enabled. 169 169 More X86-64 boot options can be found in 170 - Documentation/x86/x86_64/boot-options.txt . 170 + Documentation/x86/x86_64/boot-options.rst. 171 171 X86 Either 32-bit or 64-bit x86 (same as X86-32+X86-64) 172 172 X86_UV SGI UV support is enabled. 173 173 XEN Xen support is enabled ··· 181 181 Parameters denoted with BOOT are actually interpreted by the boot 182 182 loader, and have no meaning to the kernel directly. 183 183 Do not modify the syntax of boot loader parameters without extreme 184 - need or coordination with <Documentation/x86/boot.txt>. 184 + need or coordination with <Documentation/x86/boot.rst>. 185 185 186 186 There are also arch-specific kernel-parameters not documented here. 187 - See for example <Documentation/x86/x86_64/boot-options.txt>. 187 + See for example <Documentation/x86/x86_64/boot-options.rst>. 188 188 189 189 Note that ALL kernel parameters listed below are CASE SENSITIVE, and that 190 190 a trailing = on the name of any parameter states that that parameter will
+8 -8
Documentation/admin-guide/kernel-parameters.txt
··· 53 53 ACPI_DEBUG_PRINT statements, e.g., 54 54 ACPI_DEBUG_PRINT((ACPI_DB_INFO, ... 55 55 The debug_level mask defaults to "info". See 56 - Documentation/acpi/debug.txt for more information about 56 + Documentation/firmware-guide/acpi/debug.rst for more information about 57 57 debug layers and levels. 58 58 59 59 Enable processor driver info messages: ··· 963 963 for details. 964 964 965 965 nompx [X86] Disables Intel Memory Protection Extensions. 966 - See Documentation/x86/intel_mpx.txt for more 966 + See Documentation/x86/intel_mpx.rst for more 967 967 information about the feature. 968 968 969 969 nopku [X86] Disable Memory Protection Keys CPU feature found ··· 1189 1189 that is to be dynamically loaded by Linux. If there are 1190 1190 multiple variables with the same name but with different 1191 1191 vendor GUIDs, all of them will be loaded. See 1192 - Documentation/acpi/ssdt-overlays.txt for details. 1192 + Documentation/admin-guide/acpi/ssdt-overlays.rst for details. 1193 1193 1194 1194 1195 1195 eisa_irq_edge= [PARISC,HW] ··· 2383 2383 2384 2384 mce [X86-32] Machine Check Exception 2385 2385 2386 - mce=option [X86-64] See Documentation/x86/x86_64/boot-options.txt 2386 + mce=option [X86-64] See Documentation/x86/x86_64/boot-options.rst 2387 2387 2388 2388 md= [HW] RAID subsystems devices and level 2389 2389 See Documentation/admin-guide/md.rst. ··· 2439 2439 set according to the 2440 2440 CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE kernel config 2441 2441 option. 2442 - See Documentation/memory-hotplug.txt. 2442 + See Documentation/admin-guide/mm/memory-hotplug.rst. 2443 2443 2444 2444 memmap=exactmap [KNL,X86] Enable setting of an exact 2445 2445 E820 memory map, as specified by the user. ··· 2528 2528 mem_encrypt=on: Activate SME 2529 2529 mem_encrypt=off: Do not activate SME 2530 2530 2531 - Refer to Documentation/x86/amd-memory-encryption.txt 2531 + Refer to Documentation/virtual/kvm/amd-memory-encryption.rst 2532 2532 for details on when memory encryption can be activated. 2533 2533 2534 2534 mem_sleep_default= [SUSPEND] Default system suspend mode: ··· 3529 3529 See Documentation/blockdev/paride.txt. 3530 3530 3531 3531 pirq= [SMP,APIC] Manual mp-table setup 3532 - See Documentation/x86/i386/IO-APIC.txt. 3532 + See Documentation/x86/i386/IO-APIC.rst. 3533 3533 3534 3534 plip= [PPT,NET] Parallel port network link 3535 3535 Format: { parport<nr> | timid | 0 } ··· 5055 5055 Can be used multiple times for multiple devices. 5056 5056 5057 5057 vga= [BOOT,X86-32] Select a particular video mode 5058 - See Documentation/x86/boot.txt and 5058 + See Documentation/x86/boot.rst and 5059 5059 Documentation/svga.txt. 5060 5060 Use vga=ask for menu. 5061 5061 This is actually a boot loader parameter; the value is
+1 -1
Documentation/admin-guide/ras.rst
··· 199 199 mode). 200 200 201 201 .. [#f3] For more details about the Machine Check Architecture (MCA), 202 - please read Documentation/x86/x86_64/machinecheck at the Kernel tree. 202 + please read Documentation/x86/x86_64/machinecheck.rst at the Kernel tree. 203 203 204 204 EDAC - Error Detection And Correction 205 205 *************************************
+3 -4
Documentation/devicetree/bindings/net/fsl-enetc.txt
··· 16 16 In this case, the ENETC node should include a "mdio" sub-node 17 17 that in turn should contain the "ethernet-phy" node describing the 18 18 external phy. Below properties are required, their bindings 19 - already defined in ethernet.txt or phy.txt, under 20 - Documentation/devicetree/bindings/net/*. 19 + already defined in Documentation/devicetree/bindings/net/ethernet.txt or 20 + Documentation/devicetree/bindings/net/phy.txt. 21 21 22 22 Required: 23 23 ··· 51 51 connection: 52 52 53 53 In this case, the ENETC port node defines a fixed link connection, 54 - as specified by "fixed-link.txt", under 55 - Documentation/devicetree/bindings/net/*. 54 + as specified by Documentation/devicetree/bindings/net/fixed-link.txt. 56 55 57 56 Required: 58 57
+1 -1
Documentation/devicetree/bindings/pci/amlogic,meson-pcie.txt
··· 3 3 Amlogic Meson PCIe host controller is based on the Synopsys DesignWare PCI core. 4 4 It shares common functions with the PCIe DesignWare core driver and 5 5 inherits common properties defined in 6 - Documentation/devicetree/bindings/pci/designware-pci.txt. 6 + Documentation/devicetree/bindings/pci/designware-pcie.txt. 7 7 8 8 Additional properties are described here: 9 9
+1 -1
Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txt
··· 97 97 sent for this regulator including those which are for a 98 98 strictly lower power state. 99 99 100 - Other properties defined in Documentation/devicetree/bindings/regulator.txt 100 + Other properties defined in Documentation/devicetree/bindings/regulator/regulator.txt 101 101 may also be used. regulator-initial-mode and regulator-allowed-modes may be 102 102 specified for VRM regulators using mode values from 103 103 include/dt-bindings/regulator/qcom,rpmh-regulator.h. regulator-allow-bypass
+1 -1
Documentation/devicetree/booting-without-of.txt
··· 277 277 the decompressor (the real mode entry point goes to the same 32bit 278 278 entry point once it switched into protected mode). That entry point 279 279 supports one calling convention which is documented in 280 - Documentation/x86/boot.txt 280 + Documentation/x86/boot.rst 281 281 The physical pointer to the device-tree block (defined in chapter II) 282 282 is passed via setup_data which requires at least boot protocol 2.09. 283 283 The type filed is defined as
+1 -1
Documentation/driver-api/gpio/board.rst
··· 101 101 } 102 102 103 103 For more information about the ACPI GPIO bindings see 104 - Documentation/acpi/gpio-properties.txt. 104 + Documentation/firmware-guide/acpi/gpio-properties.rst. 105 105 106 106 Platform Data 107 107 -------------
+1 -1
Documentation/driver-api/gpio/consumer.rst
··· 437 437 _DSD is not present, the mappings between GpioIo()/GpioInt() resources and GPIO 438 438 connection IDs need to be provided by device drivers. 439 439 440 - For details refer to Documentation/acpi/gpio-properties.txt 440 + For details refer to Documentation/firmware-guide/acpi/gpio-properties.rst 441 441 442 442 443 443 Interacting With the Legacy GPIO Subsystem
+1 -1
Documentation/firmware-guide/acpi/enumeration.rst
··· 339 339 There are also devm_* versions of these functions which release the 340 340 descriptors once the device is released. 341 341 342 - See Documentation/acpi/gpio-properties.txt for more information about the 342 + See Documentation/firmware-guide/acpi/gpio-properties.rst for more information about the 343 343 _DSD binding related to GPIOs. 344 344 345 345 MFD devices
+1 -1
Documentation/firmware-guide/acpi/method-tracing.rst
··· 68 68 69 69 Where: 70 70 0xXXXXXXXX/0xYYYYYYYY 71 - Refer to Documentation/acpi/debug.txt for possible debug layer/level 71 + Refer to Documentation/firmware-guide/acpi/debug.rst for possible debug layer/level 72 72 masking values. 73 73 \PPPP.AAAA.TTTT.HHHH 74 74 Full path of a control method that can be found in the ACPI namespace.
+1 -1
Documentation/i2c/instantiating-devices
··· 85 85 ------------------------------------------- 86 86 87 87 ACPI can also describe I2C devices. There is special documentation for this 88 - which is currently located at Documentation/acpi/enumeration.txt. 88 + which is currently located at Documentation/firmware-guide/acpi/enumeration.rst. 89 89 90 90 91 91 Method 2: Instantiate the devices explicitly
+2 -2
Documentation/sysctl/kernel.txt
··· 155 155 the value 340 = 0x154. 156 156 157 157 See the type_of_loader and ext_loader_type fields in 158 - Documentation/x86/boot.txt for additional information. 158 + Documentation/x86/boot.rst for additional information. 159 159 160 160 ============================================================== 161 161 ··· 167 167 file will contain the value 564 = 0x234. 168 168 169 169 See the type_of_loader and ext_loader_ver fields in 170 - Documentation/x86/boot.txt for additional information. 170 + Documentation/x86/boot.rst for additional information. 171 171 172 172 ============================================================== 173 173
+1 -1
Documentation/translations/zh_CN/process/4.Coding.rst
··· 241 241 242 242 任何添加新用户空间界面的代码(包括新的sysfs或/proc文件)都应该包含该界面的 243 243 文档,该文档使用户空间开发人员能够知道他们在使用什么。请参阅 244 - Documentation/abi/readme,了解如何格式化此文档以及需要提供哪些信息。 244 + Documentation/ABI/README,了解如何格式化此文档以及需要提供哪些信息。 245 245 246 246 文件 :ref:`Documentation/admin-guide/kernel-parameters.rst <kernelparameters>` 247 247 描述了内核的所有引导时间参数。任何添加新参数的补丁都应该向该文件添加适当的
+1 -1
Documentation/x86/x86_64/5level-paging.rst
··· 20 20 QEMU 2.9 and later support 5-level paging. 21 21 22 22 Virtual memory layout for 5-level paging is described in 23 - Documentation/x86/x86_64/mm.txt 23 + Documentation/x86/x86_64/mm.rst 24 24 25 25 26 26 Enabling 5-level paging
+2 -2
Documentation/x86/x86_64/boot-options.rst
··· 9 9 10 10 Machine check 11 11 ============= 12 - Please see Documentation/x86/x86_64/machinecheck for sysfs runtime tunables. 12 + Please see Documentation/x86/x86_64/machinecheck.rst for sysfs runtime tunables. 13 13 14 14 mce=off 15 15 Disable machine check ··· 89 89 Don't use the local APIC (alias for i386 compatibility) 90 90 91 91 pirq=... 92 - See Documentation/x86/i386/IO-APIC.txt 92 + See Documentation/x86/i386/IO-APIC.rst 93 93 94 94 noapictimer 95 95 Don't set up the APIC timer
+1 -1
Documentation/x86/x86_64/fake-numa-for-cpusets.rst
··· 18 18 Documentation/cgroup-v1/cpusets.txt. 19 19 There are a number of different configurations you can use for your needs. For 20 20 more information on the numa=fake command line option and its various ways of 21 - configuring fake nodes, see Documentation/x86/x86_64/boot-options.txt. 21 + configuring fake nodes, see Documentation/x86/x86_64/boot-options.rst. 22 22 23 23 For the purposes of this introduction, we'll assume a very primitive NUMA 24 24 emulation setup of "numa=fake=4*512,". This will split our system memory into
+2 -2
MAINTAINERS
··· 3874 3874 F: Documentation/devicetree/bindings/pinctrl/cirrus,lochnagar.txt 3875 3875 F: Documentation/devicetree/bindings/regulator/cirrus,lochnagar.txt 3876 3876 F: Documentation/devicetree/bindings/sound/cirrus,lochnagar.txt 3877 - F: Documentation/hwmon/lochnagar 3877 + F: Documentation/hwmon/lochnagar.rst 3878 3878 3879 3879 CISCO FCOE HBA DRIVER 3880 3880 M: Satish Kharat <satishkh@cisco.com> ··· 11272 11272 M: Rui Miguel Silva <rmfrfs@gmail.com> 11273 11273 L: linux-iio@vger.kernel.org 11274 11274 S: Maintained 11275 - F: Documentation/devicetree/bindings/iio/gyroscope/fxas21002c.txt 11275 + F: Documentation/devicetree/bindings/iio/gyroscope/nxp,fxas21002c.txt 11276 11276 F: drivers/iio/gyro/fxas21002c_core.c 11277 11277 F: drivers/iio/gyro/fxas21002c.h 11278 11278 F: drivers/iio/gyro/fxas21002c_i2c.c
+1 -1
arch/arm/Kconfig
··· 1263 1263 uniprocessor machines. On a uniprocessor machine, the kernel 1264 1264 will run faster if you say N here. 1265 1265 1266 - See also <file:Documentation/x86/i386/IO-APIC.txt>, 1266 + See also <file:Documentation/x86/i386/IO-APIC.rst>, 1267 1267 <file:Documentation/lockup-watchdogs.txt> and the SMP-HOWTO available at 1268 1268 <http://tldp.org/HOWTO/SMP-HOWTO.html>. 1269 1269
+1 -1
arch/arm64/kernel/kexec_image.c
··· 53 53 54 54 /* 55 55 * We require a kernel with an unambiguous Image header. Per 56 - * Documentation/booting.txt, this is the case when image_size 56 + * Documentation/arm64/booting.txt, this is the case when image_size 57 57 * is non-zero (practically speaking, since v3.17). 58 58 */ 59 59 h = (struct arm64_image_header *)kernel;
+7 -7
arch/x86/Kconfig
··· 395 395 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power 396 396 Management" code will be disabled if you say Y here. 397 397 398 - See also <file:Documentation/x86/i386/IO-APIC.txt>, 398 + See also <file:Documentation/x86/i386/IO-APIC.rst>, 399 399 <file:Documentation/lockup-watchdogs.txt> and the SMP-HOWTO available at 400 400 <http://www.tldp.org/docs.html#howto>. 401 401 ··· 1290 1290 the Linux kernel. 1291 1291 1292 1292 The preferred method to load microcode from a detached initrd is described 1293 - in Documentation/x86/microcode.txt. For that you need to enable 1293 + in Documentation/x86/microcode.rst. For that you need to enable 1294 1294 CONFIG_BLK_DEV_INITRD in order for the loader to be able to scan the 1295 1295 initrd for microcode blobs. 1296 1296 ··· 1329 1329 It is inadequate because it runs too late to be able to properly 1330 1330 load microcode on a machine and it needs special tools. Instead, you 1331 1331 should've switched to the early loading method with the initrd or 1332 - builtin microcode by now: Documentation/x86/microcode.txt 1332 + builtin microcode by now: Documentation/x86/microcode.rst 1333 1333 1334 1334 config X86_MSR 1335 1335 tristate "/dev/cpu/*/msr - Model-specific register support" ··· 1478 1478 A kernel with the option enabled can be booted on machines that 1479 1479 support 4- or 5-level paging. 1480 1480 1481 - See Documentation/x86/x86_64/5level-paging.txt for more 1481 + See Documentation/x86/x86_64/5level-paging.rst for more 1482 1482 information. 1483 1483 1484 1484 Say N if unsure. ··· 1626 1626 depends on X86_64 && MEMORY_HOTPLUG 1627 1627 help 1628 1628 This option enables a sysfs memory/probe interface for testing. 1629 - See Documentation/memory-hotplug.txt for more information. 1629 + See Documentation/admin-guide/mm/memory-hotplug.rst for more information. 1630 1630 If you are unsure how to answer this question, answer N. 1631 1631 1632 1632 config ARCH_PROC_KCORE_TEXT ··· 1783 1783 You can safely say Y even if your machine doesn't have MTRRs, you'll 1784 1784 just add about 9 KB to your kernel. 1785 1785 1786 - See <file:Documentation/x86/mtrr.txt> for more information. 1786 + See <file:Documentation/x86/mtrr.rst> for more information. 1787 1787 1788 1788 config MTRR_SANITIZER 1789 1789 def_bool y ··· 1895 1895 process and adds some branches to paths used during 1896 1896 exec() and munmap(). 1897 1897 1898 - For details, see Documentation/x86/intel_mpx.txt 1898 + For details, see Documentation/x86/intel_mpx.rst 1899 1899 1900 1900 If unsure, say N. 1901 1901
+1 -1
arch/x86/Kconfig.debug
··· 156 156 code. When you use it make sure you have a big enough 157 157 IOMMU/AGP aperture. Most of the options enabled by this can 158 158 be set more finegrained using the iommu= command line 159 - options. See Documentation/x86/x86_64/boot-options.txt for more 159 + options. See Documentation/x86/x86_64/boot-options.rst for more 160 160 details. 161 161 162 162 config IOMMU_LEAK
+1 -1
arch/x86/boot/header.S
··· 313 313 314 314 type_of_loader: .byte 0 # 0 means ancient bootloader, newer 315 315 # bootloaders know to change this. 316 - # See Documentation/x86/boot.txt for 316 + # See Documentation/x86/boot.rst for 317 317 # assigned ids 318 318 319 319 # flags, unused bits must be zero (RFU) bit within loadflags
+1 -1
arch/x86/entry/entry_64.S
··· 8 8 * 9 9 * entry.S contains the system-call and fault low-level handling routines. 10 10 * 11 - * Some of this is documented in Documentation/x86/entry_64.txt 11 + * Some of this is documented in Documentation/x86/entry_64.rst 12 12 * 13 13 * A note on terminology: 14 14 * - iret frame: Architecture defined interrupt frame from SS to RIP
+1 -1
arch/x86/include/asm/bootparam_utils.h
··· 24 24 * IMPORTANT NOTE TO BOOTLOADER AUTHORS: do not simply clear 25 25 * this field. The purpose of this field is to guarantee 26 26 * compliance with the x86 boot spec located in 27 - * Documentation/x86/boot.txt . That spec says that the 27 + * Documentation/x86/boot.rst . That spec says that the 28 28 * *whole* structure should be cleared, after which only the 29 29 * portion defined by struct setup_header (boot_params->hdr) 30 30 * should be copied in.
+1 -1
arch/x86/include/asm/page_64_types.h
··· 48 48 49 49 #define __START_KERNEL_map _AC(0xffffffff80000000, UL) 50 50 51 - /* See Documentation/x86/x86_64/mm.txt for a description of the memory map. */ 51 + /* See Documentation/x86/x86_64/mm.rst for a description of the memory map. */ 52 52 53 53 #define __PHYSICAL_MASK_SHIFT 52 54 54
+1 -1
arch/x86/include/asm/pgtable_64_types.h
··· 103 103 #define PGDIR_MASK (~(PGDIR_SIZE - 1)) 104 104 105 105 /* 106 - * See Documentation/x86/x86_64/mm.txt for a description of the memory map. 106 + * See Documentation/x86/x86_64/mm.rst for a description of the memory map. 107 107 * 108 108 * Be very careful vs. KASLR when changing anything here. The KASLR address 109 109 * range must not overlap with anything except the KASAN shadow area, which
+1 -1
arch/x86/kernel/cpu/microcode/amd.c
··· 61 61 62 62 /* 63 63 * Microcode patch container file is prepended to the initrd in cpio 64 - * format. See Documentation/x86/microcode.txt 64 + * format. See Documentation/x86/microcode.rst 65 65 */ 66 66 static const char 67 67 ucode_path[] __maybe_unused = "kernel/x86/microcode/AuthenticAMD.bin";
+1 -1
arch/x86/kernel/kexec-bzimage64.c
··· 416 416 efi_map_offset = params_cmdline_sz; 417 417 efi_setup_data_offset = efi_map_offset + ALIGN(efi_map_sz, 16); 418 418 419 - /* Copy setup header onto bootparams. Documentation/x86/boot.txt */ 419 + /* Copy setup header onto bootparams. Documentation/x86/boot.rst */ 420 420 setup_header_size = 0x0202 + kernel[0x0201] - setup_hdr_offset; 421 421 422 422 /* Is there a limit on setup header size? */
+1 -1
arch/x86/kernel/pci-dma.c
··· 70 70 } 71 71 72 72 /* 73 - * See <Documentation/x86/x86_64/boot-options.txt> for the iommu kernel 73 + * See <Documentation/x86/x86_64/boot-options.rst> for the iommu kernel 74 74 * parameter documentation. 75 75 */ 76 76 static __init int iommu_setup(char *p)
+1 -1
arch/x86/mm/tlb.c
··· 711 711 } 712 712 713 713 /* 714 - * See Documentation/x86/tlb.txt for details. We choose 33 714 + * See Documentation/x86/tlb.rst for details. We choose 33 715 715 * because it is large enough to cover the vast majority (at 716 716 * least 95%) of allocations, and is small enough that we are 717 717 * confident it will not cause too much overhead. Each single
+1 -1
arch/x86/platform/pvh/enlighten.c
··· 86 86 } 87 87 88 88 /* 89 - * See Documentation/x86/boot.txt. 89 + * See Documentation/x86/boot.rst. 90 90 * 91 91 * Version 2.12 supports Xen entry point but we will use default x86/PC 92 92 * environment (i.e. hardware_subarch 0).
+5 -5
drivers/acpi/Kconfig
··· 333 333 depends on !STANDALONE 334 334 help 335 335 This option supports a custom DSDT by linking it into the kernel. 336 - See Documentation/acpi/dsdt-override.txt 336 + See Documentation/admin-guide/acpi/dsdt-override.rst 337 337 338 338 Enter the full path name to the file which includes the AmlCode 339 339 or dsdt_aml_code declaration. ··· 355 355 This option provides functionality to upgrade arbitrary ACPI tables 356 356 via initrd. No functional change if no ACPI tables are passed via 357 357 initrd, therefore it's safe to say Y. 358 - See Documentation/acpi/initrd_table_override.txt for details 358 + See Documentation/admin-guide/acpi/initrd_table_override.rst for details 359 359 360 360 config ACPI_TABLE_OVERRIDE_VIA_BUILTIN_INITRD 361 361 bool "Override ACPI tables from built-in initrd" ··· 365 365 This option provides functionality to override arbitrary ACPI tables 366 366 from built-in uncompressed initrd. 367 367 368 - See Documentation/acpi/initrd_table_override.txt for details 368 + See Documentation/admin-guide/acpi/initrd_table_override.rst for details 369 369 370 370 config ACPI_DEBUG 371 371 bool "Debug Statements" ··· 374 374 output and increases the kernel size by around 50K. 375 375 376 376 Use the acpi.debug_layer and acpi.debug_level kernel command-line 377 - parameters documented in Documentation/acpi/debug.txt and 377 + parameters documented in Documentation/firmware-guide/acpi/debug.rst and 378 378 Documentation/admin-guide/kernel-parameters.rst to control the type and 379 379 amount of debug output. 380 380 ··· 445 445 help 446 446 This debug facility allows ACPI AML methods to be inserted and/or 447 447 replaced without rebooting the system. For details refer to: 448 - Documentation/acpi/method-customizing.txt. 448 + Documentation/firmware-guide/acpi/method-customizing.rst. 449 449 450 450 NOTE: This option is security sensitive, because it allows arbitrary 451 451 kernel memory to be written to by root (uid=0) users, allowing them
+1 -1
drivers/net/ethernet/faraday/ftgmac100.c
··· 1075 1075 } 1076 1076 1077 1077 /* Indicate that we support PAUSE frames (see comment in 1078 - * Documentation/networking/phy.txt) 1078 + * Documentation/networking/phy.rst) 1079 1079 */ 1080 1080 phy_support_asym_pause(phydev); 1081 1081
+2 -2
drivers/staging/fieldbus/Documentation/fieldbus_dev.txt
··· 54 54 a simple interface consisting of a character device and a set of sysfs files: 55 55 56 56 See: 57 - Documentation/ABI/testing/sysfs-class-fieldbus-dev 58 - Documentation/ABI/testing/fieldbus-dev-cdev 57 + drivers/staging/fieldbus/Documentation/ABI/sysfs-class-fieldbus-dev 58 + drivers/staging/fieldbus/Documentation/ABI/fieldbus-dev-cdev 59 59 60 60 Note that this simple interface does not provide a way to modify adapter 61 61 configuration settings. It is therefore useful only for adapters that get their
+1 -1
drivers/vhost/vhost.c
··· 1694 1694 1695 1695 /* TODO: This is really inefficient. We need something like get_user() 1696 1696 * (instruction directly accesses the data, with an exception table entry 1697 - * returning -EFAULT). See Documentation/x86/exception-tables.txt. 1697 + * returning -EFAULT). See Documentation/x86/exception-tables.rst. 1698 1698 */ 1699 1699 static int set_bit_to_user(int nr, void __user *addr) 1700 1700 {
+1 -1
include/acpi/acpi_drivers.h
··· 25 25 #define ACPI_MAX_STRING 80 26 26 27 27 /* 28 - * Please update drivers/acpi/debug.c and Documentation/acpi/debug.txt 28 + * Please update drivers/acpi/debug.c and Documentation/firmware-guide/acpi/debug.rst 29 29 * if you add to this list. 30 30 */ 31 31 #define ACPI_BUS_COMPONENT 0x00010000
+1 -1
include/linux/fs_context.h
··· 85 85 * Superblock creation fills in ->root whereas reconfiguration begins with this 86 86 * already set. 87 87 * 88 - * See Documentation/filesystems/mounting.txt 88 + * See Documentation/filesystems/mount_api.txt 89 89 */ 90 90 struct fs_context { 91 91 const struct fs_context_operations *ops;
+1 -1
include/linux/lsm_hooks.h
··· 77 77 * state. This is called immediately after commit_creds(). 78 78 * 79 79 * Security hooks for mount using fs_context. 80 - * [See also Documentation/filesystems/mounting.txt] 80 + * [See also Documentation/filesystems/mount_api.txt] 81 81 * 82 82 * @fs_context_dup: 83 83 * Allocate and attach a security structure to sc->security. This pointer
+1 -1
mm/Kconfig
··· 165 165 onlining policy (/sys/devices/system/memory/auto_online_blocks) which 166 166 determines what happens to newly added memory regions. Policy setting 167 167 can always be changed at runtime. 168 - See Documentation/memory-hotplug.txt for more information. 168 + See Documentation/admin-guide/mm/memory-hotplug.rst for more information. 169 169 170 170 Say Y here if you want all hot-plugged memory blocks to appear in 171 171 'online' state by default.
+1 -1
security/Kconfig
··· 62 62 ensuring that the majority of kernel addresses are not mapped 63 63 into userspace. 64 64 65 - See Documentation/x86/pti.txt for more details. 65 + See Documentation/x86/pti.rst for more details. 66 66 67 67 config SECURITY_INFINIBAND 68 68 bool "Infiniband Security Hooks"
+1 -1
tools/include/linux/err.h
··· 20 20 * Userspace note: 21 21 * The same principle works for userspace, because 'error' pointers 22 22 * fall down to the unused hole far from user space, as described 23 - * in Documentation/x86/x86_64/mm.txt for x86_64 arch: 23 + * in Documentation/x86/x86_64/mm.rst for x86_64 arch: 24 24 * 25 25 * 0000000000000000 - 00007fffffffffff (=47 bits) user space, different per mm hole caused by [48:63] sign extension 26 26 * ffffffffffe00000 - ffffffffffffffff (=2 MB) unused hole
+2 -2
tools/objtool/Documentation/stack-validation.txt
··· 21 21 which gcc sometimes uses jump tables. 22 22 23 23 (Objtool also has an 'orc generate' subcommand which generates debuginfo 24 - for the ORC unwinder. See Documentation/x86/orc-unwinder.txt in the 24 + for the ORC unwinder. See Documentation/x86/orc-unwinder.rst in the 25 25 kernel tree for more details.) 26 26 27 27 ··· 101 101 band. So it doesn't affect runtime performance and it can be 102 102 reliable even when interrupts or exceptions are involved. 103 103 104 - For more details, see Documentation/x86/orc-unwinder.txt. 104 + For more details, see Documentation/x86/orc-unwinder.rst. 105 105 106 106 c) Higher live patching compatibility rate 107 107