Fix broken documentation references at v5.2-rc1
Subsystems (42)
cover Fix broken documentation references at v5.2-rc1
There are several broken Documentation/* references within the Kernel tree. There are some reasons for several of them:
1. The acpi and x86 documentation files were renamed, but the references weren't updated;
2. The DT files have been converted to JSON format, causing them to be renamed;
3. Translated files point to future translation work still pending merge or require some action from someone that it is fluent at the translated language;
4. Some files (specially at DT) weren't accepted yet, but there are already references for them (at MAINTAINERS and on other DT files);
5. Some files got removed without addressing Documentation, with needs them to describe some things.
This series addresses problems 1 and 2, plus other random trivial breakages. Problems 3 to 5 depend on either accepting a patch or some specific knowledge. So, won't be addressed by this series.
The first 4 patches improve the documentation script to address some corner cases I detected while doing this series. The remaining ones are documentation fixes, being the last one having just trivial renaming stuff all over the Kernel tree.
After this series, only those warnings will be reported on v5.2-rc1:
Removed file without a non-trivial documentation adjustment:
Documentation/cgroup-v1/blkio-controller.txt: Documentation/block/cfq-iosched.txt Documentation/cgroup-v1/blkio-controller.txt: Documentation/block/cfq-iosched.txt
The documentation file uses cfq as an example, but it got removed recently. Some parts of doc should be re-written to use another scheduler as an example.
Files pending addition (as far as I identified, there were e-mails asking their inclusions, but it didn't happen upstream yet):
Documentation/devicetree/bindings/regulator/rohm,bd70528-regulator.txt: Documentation/devicetree/bindings/mfd/rohm,bd70528-pmic.txt Documentation/driver-api/generic-counter.rst: Documentation/ABI/testing/sys-bus-counter-generic-sysfs Documentation/driver-api/generic-counter.rst: Documentation/ABI/testing/sys-bus-counter
MAINTAINERS: Documentation/devicetree/bindings/rng/samsung,exynos5250-trng.txt
Translation files with broken stuff:
Documentation/translations/it_IT/process/adding-syscalls.rst: Documentation/translations/it_IT/filesystems/sysfs.txt Documentation/translations/it_IT/process/coding-style.rst: Documentation/translations/it_IT/kbuild/kconfig-language.txt Documentation/translations/it_IT/process/magic-number.rst: Documentation/process/magic-numbers.rst Documentation/translations/zh_CN/basic_profiling.txt: Documentation/basic_profiling Documentation/translations/zh_CN/basic_profiling.txt: Documentation/basic_profiling Documentation/translations/zh_CN/process/howto.rst: Documentation/DocBook/
Mauro Carvalho Chehab (10):
scripts/documentation-file-ref-check: better handle translations scripts/documentation-file-ref-check: exclude false-positives scripts/documentation-file-ref-check: improve tools ref handling scripts/documentation-file-ref-check: teach about .txt -> .yaml
renames
ABI: sysfs-devices-system-cpu: point to the right docs
isdn: mISDN: remove a bogus reference to a non-existing doc
mfd: madera: point to the right pinctrl binding file
dt: fix refs that were renamed to json with the same file name
dt: fix broken references to nand.txt
docs: fix broken documentation links
.../ABI/testing/sysfs-devices-system-cpu | 3 +- Documentation/acpi/dsd/leds.txt | 2 +- .../admin-guide/kernel-parameters.rst | 6 +-- .../admin-guide/kernel-parameters.txt | 16 +++---- Documentation/admin-guide/ras.rst | 2 +- .../devicetree/bindings/arm/omap/crossbar.txt | 2 +- .../bindings/clock/samsung,s5pv210-clock.txt | 2 +- .../marvell,odmi-controller.txt | 2 +- .../bindings/leds/irled/spi-ir-led.txt | 2 +- .../bindings/mtd/amlogic,meson-nand.txt | 2 +- .../devicetree/bindings/mtd/gpmc-nand.txt | 2 +- .../devicetree/bindings/mtd/marvell-nand.txt | 2 +- .../devicetree/bindings/mtd/tango-nand.txt | 2 +- .../devicetree/bindings/net/fsl-enetc.txt | 7 ++- .../bindings/pci/amlogic,meson-pcie.txt | 2 +- .../regulator/qcom,rpmh-regulator.txt | 2 +- .../devicetree/booting-without-of.txt | 2 +- Documentation/driver-api/gpio/board.rst | 2 +- Documentation/driver-api/gpio/consumer.rst | 2 +- .../firmware-guide/acpi/enumeration.rst | 2 +- .../firmware-guide/acpi/method-tracing.rst | 2 +- Documentation/i2c/instantiating-devices | 2 +- Documentation/sysctl/kernel.txt | 4 +- .../translations/it_IT/process/4.Coding.rst | 2 +- .../translations/it_IT/process/howto.rst | 2 +- .../it_IT/process/stable-kernel-rules.rst | 4 +- .../translations/zh_CN/process/4.Coding.rst | 2 +- Documentation/x86/x86_64/5level-paging.rst | 2 +- Documentation/x86/x86_64/boot-options.rst | 4 +- .../x86/x86_64/fake-numa-for-cpusets.rst | 2 +- MAINTAINERS | 10 ++--- arch/arm/Kconfig | 2 +- arch/arm64/kernel/kexec_image.c | 2 +- arch/powerpc/Kconfig | 2 +- arch/x86/Kconfig | 16 +++---- arch/x86/Kconfig.debug | 2 +- arch/x86/boot/header.S | 2 +- arch/x86/entry/entry_64.S | 2 +- arch/x86/include/asm/bootparam_utils.h | 2 +- arch/x86/include/asm/page_64_types.h | 2 +- arch/x86/include/asm/pgtable_64_types.h | 2 +- arch/x86/kernel/cpu/microcode/amd.c | 2 +- arch/x86/kernel/kexec-bzimage64.c | 2 +- arch/x86/kernel/pci-dma.c | 2 +- arch/x86/mm/tlb.c | 2 +- arch/x86/platform/pvh/enlighten.c | 2 +- drivers/acpi/Kconfig | 10 ++--- drivers/isdn/mISDN/dsp_core.c | 2 - drivers/net/ethernet/faraday/ftgmac100.c | 2 +- .../fieldbus/Documentation/fieldbus_dev.txt | 4 +- drivers/vhost/vhost.c | 2 +- include/acpi/acpi_drivers.h | 2 +- include/linux/fs_context.h | 2 +- include/linux/lsm_hooks.h | 2 +- include/linux/mfd/madera/pdata.h | 3 +- mm/Kconfig | 2 +- scripts/documentation-file-ref-check | 44 +++++++++++++++---- security/Kconfig | 2 +- tools/include/linux/err.h | 2 +- .../Documentation/stack-validation.txt | 4 +- tools/testing/selftests/x86/protection_keys.c | 2 +- 61 files changed, 127 insertions(+), 102 deletions(-)
Signature · 1 line
2.21.0
PATCH 1/10 scripts/documentation-file-ref-check: better handle translations
Only seek for translation renames inside the translation directory.
--- scripts/documentation-file-ref-check | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-)
scripts/documentation-file-ref-check +7 -3
@@ -141,6 +141,10 @@ print "Auto-fixing broken references. Please double-check the results\n"; foreach my $ref (keys %broken_ref) { my $new =$ref; + my $basedir = "."; + # On translations, only seek inside the translations directory + $basedir = $1 if ($ref =~ m,(Documentation/translations/[^/]+),); + # get just the basename $new =~ s,.*/,,;
@@ -161,18 +165,18 @@ foreach my $ref (keys %broken_ref) { # usual reason for breakage: file renamed to .rst if (!$f) { $new =~ s/\.txt$/.rst/; - $f=qx(find . -iname $new) if ($new); + $f=qx(find $basedir -iname $new) if ($new); } # usual reason for breakage: use dash or underline if (!$f) { $new =~ s/[-_]/[-_]/g; - $f=qx(find . -iname $new) if ($new); + $f=qx(find $basedir -iname $new) if ($new); } # Wild guess: seek for the same name on another place if (!$f) { - $f = qx(find . -iname $new) if ($new); + $f = qx(find $basedir -iname $new) if ($new); } my @find = split /\s+/, $f;
Signature · 1 line
2.21.0
PATCH 2/10 scripts/documentation-file-ref-check: exclude false-positives
In reply to Mauro Carvalho ChehabThere are at least two cases where a documentation file was gone for good, but the text still mentions it:
1) drivers/vhost/vhost.c:
the reference for Documentation/virtual/lguest/lguest.c is just to give credits to the original work that vhost replaced;
2) Documentation/scsi/scsi_mid_low_api.txt:
It gives credit and mentions the old Documentation/Configure.help file that used to be part of Kernel 2.4.x
As we don't want to keep the script to keep pinpoint to those every time, let's add a logic at the script to allow it to ignore valid false-positives like the above.
--- scripts/documentation-file-ref-check | 13 +++++++++++++ 1 file changed, 13 insertions(+)
scripts/documentation-file-ref-check +13 -0
@@ -8,6 +8,14 @@ use warnings; use strict; use Getopt::Long qw(:config no_auto_abbrev); +# NOTE: only add things here when the file was gone, but the text wants +# to mention a past documentation file, for example, to give credits for +# the original work. +my %false_positives = ( + "Documentation/scsi/scsi_mid_low_api.txt" => "Documentation/Configure.help", + "drivers/vhost/vhost.c" => "Documentation/virtual/lguest/lguest.c", +); + my $scriptname = $0; $scriptname =~ s,.*/([^/]+/),$1,;
@@ -122,6 +130,11 @@ while (<IN>) { next if (grep -e, glob("$path/$ref $path/$fulref")); } + # Discard known false-positives + if (defined($false_positives{$f})) { + next if ($false_positives{$f} eq $fulref); + } + if ($fix) { if (!($ref =~ m/(scripts|Kconfig|Kbuild)/)) { $broken_ref{$ref}++;
Signature · 1 line
2.21.0
PATCH 3/10 scripts/documentation-file-ref-check: improve tools ref handling
In reply to Mauro Carvalho ChehabThere's a false positive on perf/util:
tools/perf/util/s390-cpumsf.c: Documentation/perf.data-file-format.txt
The file is there at tools/perf/Documentation/, but the logic with detects relative documentation references inside tools is not capable of detecting it.
So, improve it.
--- scripts/documentation-file-ref-check | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
scripts/documentation-file-ref-check +1 -1
@@ -127,7 +127,7 @@ while (<IN>) { if ($f =~ m/tools/) { my $path = $f; $path =~ s,(.*)/.*,$1,; - next if (grep -e, glob("$path/$ref $path/$fulref")); + next if (grep -e, glob("$path/$ref $path/../$ref $path/$fulref")); } # Discard known false-positives
Signature · 1 line
2.21.0
PATCH 4/10 scripts/documentation-file-ref-check: teach about .txt -> .yaml renames
In reply to Mauro Carvalho ChehabAt DT, files are being renamed to jason. Teach the script how to handle such renames when used in fix mode.
--- scripts/documentation-file-ref-check | 19 ++++++++++++++----- 1 file changed, 14 insertions(+), 5 deletions(-)
scripts/documentation-file-ref-check +14 -5
@@ -165,13 +165,22 @@ foreach my $ref (keys %broken_ref) { # usual reason for breakage: DT file moved around if ($ref =~ /devicetree/) { - my $search = $new; - $search =~ s,^.*/,,; - $f = qx(find Documentation/devicetree/ -iname "*$search*") if ($search); + # usual reason for breakage: DT file renamed to .yaml if (!$f) { - # Manufacturer name may have changed - $search =~ s/^.*,//; + my $new_ref = $ref; + $new_ref =~ s/\.txt$/.yaml/; + $f=$new_ref if (-f $new_ref); + } + + if (!$f) { + my $search = $new; + $search =~ s,^.*/,,; $f = qx(find Documentation/devicetree/ -iname "*$search*") if ($search); + if (!$f) { + # Manufacturer name may have changed + $search =~ s/^.*,//; + $f = qx(find Documentation/devicetree/ -iname "*$search*") if ($search); + } } }
Signature · 1 line
2.21.0
PATCH 5/10 ABI: sysfs-devices-system-cpu: point to the right docs
In reply to Mauro Carvalho ChehabThe cpuidle doc was split on two, one at the admin guide and another one at the driver API guide. Instead of pointing to a non-existent file, point to both (admin guide being the first one).
--- Documentation/ABI/testing/sysfs-devices-system-cpu | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
Documentation/ABI/testing/sysfs-devices-system-cpu +2 -1
@@ -137,7 +137,8 @@ Description: Discover cpuidle policy and mechanism current_governor: (RW) displays current idle policy. Users can switch the governor at runtime by writing to this file. - See files in Documentation/cpuidle/ for more information. + See Documentation/admin-guide/pm/cpuidle.rst and + Documentation/driver-api/pm/cpuidle.rst for more information. What: /sys/devices/system/cpu/cpuX/cpuidle/stateN/name
Signature · 1 line
2.21.0
PATCH 6/10 isdn: mISDN: remove a bogus reference to a non-existing doc
In reply to Mauro Carvalho ChehabThe mISDN driver was added on those commits:
960366cf8dbb ("Add mISDN DSP")
1b2b03f8e514 ("Add mISDN core files")
04578dd330f1 ("Define AF_ISDN and PF_ISDN")
e4ac9bc1f668 ("Add mISDN driver")None of them added a Documentation/isdn/mISDN.cert file. Also, whatever were supposed to be written there on that time, probably doesn't make any sense nowadays, as I doubt isdn would have any massive changes.
So, let's just get rid of the broken reference, in order to shut up a warning produced by ./scripts/documentation-file-ref-check.
--- drivers/isdn/mISDN/dsp_core.c | 2 -- 1 file changed, 2 deletions(-)
drivers/isdn/mISDN/dsp_core.c +0 -2
@@ -4,8 +4,6 @@* Karsten Keil ([email protected]) * * This file is (c) under GNU PUBLIC LICENSE -* For changes and modifications please read -* ../../../Documentation/isdn/mISDN.cert * * Thanks to Karsten Keil (great drivers) * Cologne Chip (great chips)
Signature · 1 line
2.21.0
PATCH 7/10 mfd: madera: point to the right pinctrl binding file
In reply to Mauro Carvalho ChehabThe reference to Documentation/pinctrl.txt doesn't exist, but there is an specific binding for the madera driver.
So, point to it.
--- include/linux/mfd/madera/pdata.h | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
include/linux/mfd/madera/pdata.h +2 -1
@@ -34,7 +34,8 @@ struct madera_codec_pdata;* @micvdd: Substruct of pdata for the MICVDD regulator * @irq_flags: Mode for primary IRQ (defaults to active low) * @gpio_base: Base GPIO number -* @gpio_configs: Array of GPIO configurations (See Documentation/pinctrl.txt) +* @gpio_configs: Array of GPIO configurations +* (See Documentation/devicetree/bindings/pinctrl/cirrus,madera-pinctrl.txt) * @n_gpio_configs: Number of entries in gpio_configs * @gpsw: General purpose switch mode setting. Depends on the external * hardware connected to the switch. (See the SW1_MODE field
Signature · 1 line
2.21.0
Charles Keepax
maintainerRe: [PATCH 07/10] mfd: madera: point to the right pinctrl binding file
Quoted 15 lines · Mauro Carvalho Chehab
The reference to
Documentation/pinctrl.txtdoesn't exist, but there is an specific binding for the madera driver.So, point to it.
Signed-off-by Mauro Carvalho Chehab <[email protected]>--- include/linux/mfd/madera/pdata.h | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)include/linux/mfd/madera/pdata.h +0
-0
include/linux/mfd/madera/pdata.h struct madera_codec_pdata; · line 38
Quoted 6 lines
include/linux/mfd/madera/pdata.h +2
-1@@ -34,7 +34,8 @@ struct madera_codec_pdata;* @micvdd: Substruct of pdata for the MICVDD regulator * @irq_flags: Mode for primary IRQ (defaults to active low) * @gpio_base: Base GPIO number -* @gpio_configs: Array of GPIO configurations (See Documentation/pinctrl.txt) +* @gpio_configs: Array of GPIO configurations +* (See Documentation/devicetree/bindings/pinctrl/cirrus,madera-pinctrl.txt)
I believe this is trying to point at the generic pinctrl docs which now live here:
Documentation/driver-api/pinctl.rst
There is a patch to do this already:
https://lkml.org/lkml/2019/1/9/853
With the latest resend here:
https://www.mail-archive.com/[email protected]/msg2001752.html
Thanks,
Charles
Quoted 6 lines
include/linux/mfd/madera/pdata.h +0
-0* @n_gpio_configs: Number of entries in gpio_configs * @gpsw: General purpose switch mode setting. Depends on the external * hardware connected to the switch. (See the SW1_MODE field Signature · 1 line
2.21.0
Re: [PATCH 07/10] mfd: madera: point to the right pinctrl binding file
Em Mon, 20 May 2019 16:42:45 +0100
Charles Keepax <[email protected]> escreveu:
Quoted 26 lines · Mauro Carvalho Chehab
Quoted 15 lines
The reference to
Documentation/pinctrl.txtdoesn't exist, but there is an specific binding for the madera driver.So, point to it.
Signed-off-by Mauro Carvalho Chehab <[email protected]>--- include/linux/mfd/madera/pdata.h | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)include/linux/mfd/madera/pdata.h +0
-0include/linux/mfd/madera/pdata.h struct madera_codec_pdata; · line 38
Quoted 6 lines
include/linux/mfd/madera/pdata.h +2
-1@@ -34,7 +34,8 @@ struct madera_codec_pdata;* @micvdd: Substruct of pdata for the MICVDD regulator * @irq_flags: Mode for primary IRQ (defaults to active low) * @gpio_base: Base GPIO number -* @gpio_configs: Array of GPIO configurations (See Documentation/pinctrl.txt) +* @gpio_configs: Array of GPIO configurations +* (See Documentation/devicetree/bindings/pinctrl/cirrus,madera-pinctrl.txt) I believe this is trying to point at the generic pinctrl docs which now live here:
Quoted 6 lines
Documentation/driver-api/pinctl.rstThere is a patch to do this already:
https://lkml.org/lkml/2019/1/9/853
With the latest resend here:
https://www.mail-archive.com/[email protected]/msg2001752.html
Ah, makes sense to me.
Please ignore this one.
Thanks,
Mauro
PATCH 8/10 dt: fix refs that were renamed to json with the same file name
In reply to Mauro Carvalho ChehabThis file was converted to json, but the references weren't renamed.
(and other similar commits)
--- Documentation/devicetree/bindings/arm/omap/crossbar.txt | 2 +- .../devicetree/bindings/clock/samsung,s5pv210-clock.txt | 2 +- .../bindings/interrupt-controller/marvell,odmi-controller.txt | 2 +- Documentation/devicetree/bindings/leds/irled/spi-ir-led.txt | 2 +- MAINTAINERS | 4 ++-- 5 files changed, 6 insertions(+), 6 deletions(-)
Documentation/devicetree/bindings/arm/omap/crossbar.txt +1 -1
@@ -41,7 +41,7 @@ Examples: Consumer: ======== See Documentation/devicetree/bindings/interrupt-controller/interrupts.txt and -Documentation/devicetree/bindings/interrupt-controller/arm,gic.txt for +Documentation/devicetree/bindings/interrupt-controller/arm,gic.yaml for further details. An interrupt consumer on an SoC using crossbar will use:
Documentation/devicetree/bindings/clock/samsung,s5pv210-clock.txt +1 -1
@@ -35,7 +35,7 @@ board device tree, including the system base clock, as selected by XOM[0] pin of the SoC. Refer to generic fixed rate clock bindings documentation[1] for more information how to specify these clocks. -[1] Documentation/devicetree/bindings/clock/fixed-clock.txt +[1] Documentation/devicetree/bindings/clock/fixed-clock.yaml Example: Clock controller node:
Documentation/devicetree/bindings/interrupt-controller/marvell,odmi-controller.txt +1 -1
@@ -23,7 +23,7 @@ Required properties: - marvell,spi-base : List of GIC base SPI interrupts, one for each ODMI frame. Those SPI interrupts are 0-based, i.e marvell,spi-base = <128> will use SPI #96. - See Documentation/devicetree/bindings/interrupt-controller/arm,gic.txt + See Documentation/devicetree/bindings/interrupt-controller/arm,gic.yaml for details about the GIC Device Tree binding. Example:
Documentation/devicetree/bindings/leds/irled/spi-ir-led.txt +1 -1
@@ -15,7 +15,7 @@ Optional properties: - power-supply: specifies the power source. It can either be a regulator or a gpio which enables a regulator, i.e. a regulator-fixed as described in - Documentation/devicetree/bindings/regulator/fixed-regulator.txt + Documentation/devicetree/bindings/regulator/fixed-regulator.yaml Example:
MAINTAINERS +2 -2
@@ -2768,7 +2768,7 @@ AVIA HX711 ANALOG DIGITAL CONVERTER IIO DRIVER M: Andreas Klinger <[email protected]> L: [email protected] S: Maintained -F: Documentation/devicetree/bindings/iio/adc/avia-hx711.txt +F: Documentation/devicetree/bindings/iio/adc/avia-hx711.yaml F: drivers/iio/adc/hx711.c AX.25 NETWORK LAYER
@@ -14353,7 +14353,7 @@ SIMPLEFB FB DRIVER M: Hans de Goede <[email protected]> L: [email protected] S: Maintained -F: Documentation/devicetree/bindings/display/simple-framebuffer.txt +F: Documentation/devicetree/bindings/display/simple-framebuffer.yaml F: drivers/video/fbdev/simplefb.c F: include/linux/platform_data/simplefb.h
Signature · 1 line
2.21.0
Re: [PATCH 08/10] dt: fix refs that were renamed to json with the same file name
Quoted 2 lines · Mauro Carvalho Chehab
This file was converted to json, but the references weren't
Technically, converted to json-schema (the language) or yaml (the format).
Quoted 5 lines
renamed.
Fixes 66ed144f147a ("dt-bindings: interrupt-controller: Convert ARM GIC to json-schema")(and other similar commits)
Quoted 8 lines
Signed-off-by Mauro Carvalho Chehab <[email protected]>--- Documentation/devicetree/bindings/arm/omap/crossbar.txt | 2 +- .../devicetree/bindings/clock/samsung,s5pv210-clock.txt | 2 +- .../bindings/interrupt-controller/marvell,odmi-controller.txt | 2 +- Documentation/devicetree/bindings/leds/irled/spi-ir-led.txt | 2 +- MAINTAINERS | 4 ++-- 5 files changed, 6 insertions(+), 6 deletions(-)
FYI, I'm actively looking for this in conversions now as we've had a few of these. For cases where we have a lot of references, I'm fixing this by keeping the .txt file with a reference to the .yaml file.
I'll pick up the DT patches in the series.
Rob
Re: [PATCH 08/10] dt: fix refs that were renamed to json with the same file name
Em Mon, 20 May 2019 10:57:47 -0500
Rob Herring <[email protected]> escreveu:
Quoted 6 lines
Quoted 2 lines · Mauro Carvalho Chehab
This file was converted to json, but the references weren't
Technically, converted to json-schema (the language) or yaml (the format).
Ok. Do you want me to change it at the patch and resend?
Quoted 15 lines
Quoted 6 lines
renamed.
Fixes 66ed144f147a ("dt-bindings: interrupt-controller: Convert ARM GIC to json-schema")(and other similar commits)
Quoted 8 lines
Signed-off-by Mauro Carvalho Chehab <[email protected]>--- Documentation/devicetree/bindings/arm/omap/crossbar.txt | 2 +- .../devicetree/bindings/clock/samsung,s5pv210-clock.txt | 2 +- .../bindings/interrupt-controller/marvell,odmi-controller.txt | 2 +- Documentation/devicetree/bindings/leds/irled/spi-ir-led.txt | 2 +- MAINTAINERS | 4 ++-- 5 files changed, 6 insertions(+), 6 deletions(-)
Quoted 3 lines
FYI, I'm actively looking for this in conversions now as we've had a few of these. For cases where we have a lot of references, I'm fixing this by keeping the .txt file with a reference to the .yaml file.
If the file name remains with the same name, except for the .txt -> .yaml, you can just run the "scripts/documentation-file-ref-check --fix" after this patch:
Subject: [PATCH 04/10] scripts/documentation-file-ref-check: teach about .txt -> .yaml renames
and it should detect and automatically fix all the references. As any auto-hint script, you need to double-check the results.
Quoted 1 line
I'll pick up the DT patches in the series.
OK. There are a few such fixes inside patch 10/10. Do you want me to split it or can it go through Jonathan's doc tree?
Thanks,
Mauro
Re: [PATCH 08/10] dt: fix refs that were renamed to json with the same file name
Quoted 4 lines · Mauro Carvalho Chehab
Em Mon, 20 May 2019 10:57:47 -0500
Rob Herring <[email protected]> escreveu:
Quoted 8 lines
Quoted 6 lines
Quoted 2 lines · Mauro Carvalho Chehab
This file was converted to json, but the references weren't
Technically, converted to json-schema (the language) or yaml (the format).
Ok. Do you want me to change it at the patch and resend?
No, I can fixup.
Quoted 20 lines
Quoted 16 lines
Quoted 7 lines
renamed.
Fixes 66ed144f147a ("dt-bindings: interrupt-controller: Convert ARM GIC to json-schema")(and other similar commits)
Quoted 8 lines
Signed-off-by Mauro Carvalho Chehab <[email protected]>--- Documentation/devicetree/bindings/arm/omap/crossbar.txt | 2 +- .../devicetree/bindings/clock/samsung,s5pv210-clock.txt | 2 +- .../bindings/interrupt-controller/marvell,odmi-controller.txt | 2 +- Documentation/devicetree/bindings/leds/irled/spi-ir-led.txt | 2 +- MAINTAINERS | 4 ++-- 5 files changed, 6 insertions(+), 6 deletions(-)Quoted 3 lines
FYI, I'm actively looking for this in conversions now as we've had a few of these. For cases where we have a lot of references, I'm fixing this by keeping the .txt file with a reference to the .yaml file.
Quoted 8 lines
If the file name remains with the same name, except for the .txt -> .yaml, you can just run the "
scripts/documentation-file-ref-check--fix" after this patch:Subject: [PATCH 04/10] scripts/documentation-file-ref-check: teach about .txt -> .yaml renamesand it should detect and automatically fix all the references. As any auto-hint script, you need to double-check the results.
Nice!
Quoted 5 lines
Quoted 2 lines
I'll pick up the DT patches in the series.
OK. There are a few such fixes inside patch 10/10. Do you want me to split it or can it go through Jonathan's doc tree?
Jon's tree is fine.
Rob
PATCH 9/10 dt: fix broken references to nand.txt
In reply to Mauro Carvalho ChehabThe Documentation/devicetree/bindings/mtd/nand.txt were both renamed and converted to YAML on a single patch, without updating references to it. That caused several cross-references to break.
--- Documentation/devicetree/bindings/mtd/amlogic,meson-nand.txt | 2 +- Documentation/devicetree/bindings/mtd/gpmc-nand.txt | 2 +- Documentation/devicetree/bindings/mtd/marvell-nand.txt | 2 +- Documentation/devicetree/bindings/mtd/tango-nand.txt | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-)
Documentation/devicetree/bindings/mtd/amlogic,meson-nand.txt +1 -1
@@ -24,7 +24,7 @@ Optional children nodes: Children nodes represent the available nand chips. Other properties: -see Documentation/devicetree/bindings/mtd/nand.txt for generic bindings. +see Documentation/devicetree/bindings/mtd/nand-controller.yaml for generic bindings. Example demonstrate on AXG SoC:
Documentation/devicetree/bindings/mtd/gpmc-nand.txt +1 -1
@@ -8,7 +8,7 @@ explained in a separate documents - please refer to Documentation/devicetree/bindings/memory-controllers/omap-gpmc.txt For NAND specific properties such as ECC modes or bus width, please refer to -Documentation/devicetree/bindings/mtd/nand.txt +Documentation/devicetree/bindings/mtd/nand-controller.yaml Required properties:
Documentation/devicetree/bindings/mtd/marvell-nand.txt +1 -1
@@ -58,7 +58,7 @@ Optional properties: Step sizes are not completely random for all and follow certain patterns described in AN-379, "Marvell SoC NFC ECC". -See Documentation/devicetree/bindings/mtd/nand.txt for more details on +See Documentation/devicetree/bindings/mtd/nand-controller.yaml for more details on generic bindings.
Documentation/devicetree/bindings/mtd/tango-nand.txt +1 -1
@@ -11,7 +11,7 @@ Required properties: - #size-cells: <0> Children nodes represent the available NAND chips. -See Documentation/devicetree/bindings/mtd/nand.txt for generic bindings. +See Documentation/devicetree/bindings/mtd/nand-controller.yaml for generic bindings. Example:
Signature · 1 line
2.21.0
Re: [PATCH 09/10] dt: fix broken references to nand.txt
Hi Mauro,
Mauro Carvalho Chehab <[email protected]> wrote on Mon, 20 May 2019 11:47:38 -0300:
Quoted 7 lines
The
Documentation/devicetree/bindings/mtd/nand.txtwere both renamed and converted to YAML on a single patch, without updating references to it. That caused several cross-references to break.Fixes 212e49693592 ("dt-bindings: mtd: Add YAML schemas for the generic NAND options")Signed-off-by Mauro Carvalho Chehab <[email protected]>
Thanks for fixing it,
Miquèl
PATCH 10/10 docs: fix broken documentation links
In reply to Mauro Carvalho ChehabMostly due to x86 and acpi conversion, several documentation links are still pointing to the old file. Fix them.
--- Documentation/acpi/dsd/leds.txt | 2 +- Documentation/admin-guide/kernel-parameters.rst | 6 +++--- Documentation/admin-guide/kernel-parameters.txt | 16 ++++++++-------- Documentation/admin-guide/ras.rst | 2 +- .../devicetree/bindings/net/fsl-enetc.txt | 7 +++---- .../bindings/pci/amlogic,meson-pcie.txt | 2 +- .../bindings/regulator/qcom,rpmh-regulator.txt | 2 +- Documentation/devicetree/booting-without-of.txt | 2 +- Documentation/driver-api/gpio/board.rst | 2 +- Documentation/driver-api/gpio/consumer.rst | 2 +- .../firmware-guide/acpi/enumeration.rst | 2 +- .../firmware-guide/acpi/method-tracing.rst | 2 +- Documentation/i2c/instantiating-devices | 2 +- Documentation/sysctl/kernel.txt | 4 ++-- .../translations/it_IT/process/4.Coding.rst | 2 +- .../translations/it_IT/process/howto.rst | 2 +- .../it_IT/process/stable-kernel-rules.rst | 4 ++-- .../translations/zh_CN/process/4.Coding.rst | 2 +- Documentation/x86/x86_64/5level-paging.rst | 2 +- Documentation/x86/x86_64/boot-options.rst | 4 ++-- .../x86/x86_64/fake-numa-for-cpusets.rst | 2 +- MAINTAINERS | 6 +++--- arch/arm/Kconfig | 2 +- arch/arm64/kernel/kexec_image.c | 2 +- arch/powerpc/Kconfig | 2 +- arch/x86/Kconfig | 16 ++++++++-------- arch/x86/Kconfig.debug | 2 +- arch/x86/boot/header.S | 2 +- arch/x86/entry/entry_64.S | 2 +- arch/x86/include/asm/bootparam_utils.h | 2 +- arch/x86/include/asm/page_64_types.h | 2 +- arch/x86/include/asm/pgtable_64_types.h | 2 +- arch/x86/kernel/cpu/microcode/amd.c | 2 +- arch/x86/kernel/kexec-bzimage64.c | 2 +- arch/x86/kernel/pci-dma.c | 2 +- arch/x86/mm/tlb.c | 2 +- arch/x86/platform/pvh/enlighten.c | 2 +- drivers/acpi/Kconfig | 10 +++++----- drivers/net/ethernet/faraday/ftgmac100.c | 2 +- .../fieldbus/Documentation/fieldbus_dev.txt | 4 ++-- drivers/vhost/vhost.c | 2 +- include/acpi/acpi_drivers.h | 2 +- include/linux/fs_context.h | 2 +- include/linux/lsm_hooks.h | 2 +- mm/Kconfig | 2 +- security/Kconfig | 2 +- tools/include/linux/err.h | 2 +- tools/objtool/Documentation/stack-validation.txt | 4 ++-- tools/testing/selftests/x86/protection_keys.c | 2 +- 49 files changed, 78 insertions(+), 79 deletions(-)
Documentation/acpi/dsd/leds.txt +1 -1
@@ -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
Documentation/admin-guide/kernel-parameters.rst +3 -3
@@ -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
Documentation/admin-guide/kernel-parameters.txt +8 -8
@@ -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/x86/amd-memory-encryption.rst for details on when memory encryption can be activated. mem_sleep_default= [SUSPEND] Default system suspend mode:
@@ -3528,7 +3528,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 }
@@ -5054,7 +5054,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
Documentation/admin-guide/ras.rst +1 -1
@@ -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 *************************************
Documentation/devicetree/bindings/net/fsl-enetc.txt +3 -4
@@ -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:
Documentation/devicetree/bindings/pci/amlogic,meson-pcie.txt +1 -1
@@ -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:
Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txt +1 -1
@@ -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
Documentation/devicetree/booting-without-of.txt +1 -1
@@ -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
Documentation/driver-api/gpio/board.rst +1 -1
@@ -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 -------------
Documentation/driver-api/gpio/consumer.rst +1 -1
@@ -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
Documentation/firmware-guide/acpi/enumeration.rst +1 -1
@@ -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
Documentation/firmware-guide/acpi/method-tracing.rst +1 -1
@@ -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.
Documentation/i2c/instantiating-devices +1 -1
@@ -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
Documentation/sysctl/kernel.txt +2 -2
@@ -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. ==============================================================
Documentation/translations/it_IT/process/4.Coding.rst +1 -1
@@ -370,7 +370,7 @@ con cosa stanno lavorando. Consultate: Documentation/ABI/README per avere una descrizione di come questi documenti devono essere impostati e quali informazioni devono essere fornite. -Il file :ref:`Documentation/translations/it_IT/admin-guide/kernel-parameters.rst <kernelparameters>` +Il file :ref:`Documentation/admin-guide/kernel-parameters.rst <kernelparameters>` descrive tutti i parametri di avvio del kernel. Ogni patch che aggiunga nuovi parametri dovrebbe aggiungere nuove voci a questo file.
Documentation/translations/it_IT/process/howto.rst +1 -1
@@ -131,7 +131,7 @@ Di seguito una lista di file che sono presenti nei sorgente del kernel e che "Linux kernel patch submission format" http://linux.yyz.us/patch-format.html - :ref:`Documentation/process/translations/it_IT/stable-api-nonsense.rst <it_stable_api_nonsense>` + :ref:`Documentation/translations/it_IT/process/stable-api-nonsense.rst <it_stable_api_nonsense>` Questo file descrive la motivazioni sottostanti la conscia decisione di non avere un API stabile all'interno del kernel, incluso cose come:
Documentation/translations/it_IT/process/stable-kernel-rules.rst +2 -2
@@ -33,7 +33,7 @@ Regole sul tipo di patch che vengono o non vengono accettate nei sorgenti - Non deve includere alcuna correzione "banale" (correzioni grammaticali, pulizia dagli spazi bianchi, eccetera). - Deve rispettare le regole scritte in - :ref:`Documentation/translation/it_IT/process/submitting-patches.rst <it_submittingpatches>` + :ref:`Documentation/translations/it_IT/process/submitting-patches.rst <it_submittingpatches>` - Questa patch o una equivalente deve esistere già nei sorgenti principali di Linux
@@ -43,7 +43,7 @@ Procedura per sottomettere patch per i sorgenti -stable - Se la patch contiene modifiche a dei file nelle cartelle net/ o drivers/net, allora seguite le linee guida descritte in - :ref:`Documentation/translation/it_IT/networking/netdev-FAQ.rst <it_netdev-FAQ>`; + :ref:`Documentation/translations/it_IT/networking/netdev-FAQ.rst <it_netdev-FAQ>`; ma solo dopo aver verificato al seguente indirizzo che la patch non sia già in coda: https://patchwork.ozlabs.org/bundle/davem/stable/?series=&submitter=&state=*&q=&archive=
Documentation/translations/zh_CN/process/4.Coding.rst +1 -1
@@ -241,7 +241,7 @@ scripts/coccinelle目录下已经打包了相当多的内核“语义补丁” 任何添加新用户空间界面的代码(包括新的sysfs或/proc文件)都应该包含该界面的 文档,该文档使用户空间开发人员能够知道他们在使用什么。请参阅 -Documentation/abi/readme,了解如何格式化此文档以及需要提供哪些信息。 +Documentation/ABI/README,了解如何格式化此文档以及需要提供哪些信息。 文件 :ref:`Documentation/admin-guide/kernel-parameters.rst <kernelparameters>` 描述了内核的所有引导时间参数。任何添加新参数的补丁都应该向该文件添加适当的
Documentation/x86/x86_64/5level-paging.rst +1 -1
@@ -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
Documentation/x86/x86_64/boot-options.rst +2 -2
@@ -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
Documentation/x86/x86_64/fake-numa-for-cpusets.rst +1 -1
@@ -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
MAINTAINERS +3 -3
@@ -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 <[email protected]>
@@ -11272,7 +11272,7 @@ NXP FXAS21002C DRIVER M: Rui Miguel Silva <[email protected]> L: [email protected] 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
@@ -13043,7 +13043,7 @@ M: Niklas Cassel <[email protected]> L: [email protected] S: Maintained F: drivers/net/ethernet/stmicro/stmmac/dwmac-qcom-ethqos.c -F: Documentation/devicetree/bindings/net/qcom,dwmac.txt +F: Documentation/devicetree/bindings/net/qcom,ethqos.txt QUALCOMM GENERIC INTERFACE I2C DRIVER M: Alok Chauhan <[email protected]>
arch/arm/Kconfig +1 -1
@@ -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>.
arch/arm64/kernel/kexec_image.c +1 -1
@@ -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;
arch/powerpc/Kconfig +1 -1
@@ -898,7 +898,7 @@ config PPC_MEM_KEYS page-based protections, but without requiring modification of the page tables when an application changes protection domains. - For details, see Documentation/vm/protection-keys.rst + For details, see Documentation/x86/protection-keys.rst If unsure, say y.
arch/x86/Kconfig +8 -8
@@ -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.
@@ -1911,7 +1911,7 @@ config X86_INTEL_MEMORY_PROTECTION_KEYS page-based protections, but without requiring modification of the page tables when an application changes protection domains. - For details, see Documentation/x86/protection-keys.txt + For details, see Documentation/x86/protection-keys.rst If unsure, say y.
arch/x86/Kconfig.debug +1 -1
@@ -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
arch/x86/boot/header.S +1 -1
@@ -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
arch/x86/entry/entry_64.S +1 -1
@@ -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
arch/x86/include/asm/bootparam_utils.h +1 -1
@@ -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.
arch/x86/include/asm/page_64_types.h +1 -1
@@ -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
arch/x86/include/asm/pgtable_64_types.h +1 -1
@@ -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
arch/x86/kernel/cpu/microcode/amd.c +1 -1
@@ -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" ;
arch/x86/kernel/kexec-bzimage64.c +1 -1
@@ -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? */
arch/x86/kernel/pci-dma.c +1 -1
@@ -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)
arch/x86/mm/tlb.c +1 -1
@@ -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
arch/x86/platform/pvh/enlighten.c +1 -1
@@ -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).
drivers/acpi/Kconfig +5 -5
@@ -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
drivers/net/ethernet/faraday/ftgmac100.c +1 -1
@@ -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);
drivers/staging/fieldbus/Documentation/fieldbus_dev.txt +2 -2
@@ -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
drivers/vhost/vhost.c +1 -1
@@ -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) {
include/acpi/acpi_drivers.h +1 -1
@@ -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
include/linux/fs_context.h +1 -1
@@ -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;
include/linux/lsm_hooks.h +1 -1
@@ -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
mm/Kconfig +1 -1
@@ -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.
security/Kconfig +1 -1
@@ -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"
tools/include/linux/err.h +1 -1
@@ -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
tools/objtool/Documentation/stack-validation.txt +2 -2
@@ -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
tools/testing/selftests/x86/protection_keys.c +1 -1
@@ -1,6 +1,6 @@// SPDX-License-Identifier: GPL-2.0 /* -* Tests x86 Memory Protection Keys (see Documentation/x86/protection-keys.txt) +* Tests x86 Memory Protection Keys (see Documentation/x86/protection-keys.rst) * * There are examples in here of: * * how to set protection keys on memory
Signature · 6 lines
2.21.0 _______________________________________________ Virtualization mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/virtualization
Re: [PATCH 10/10] docs: fix broken documentation links
Quoted 4 lines · Mauro Carvalho Chehab
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 <[email protected]>
Thanks, didn't notice that.
Quoted 1 line
Documentation/i2c/instantiating-devices | 2 +-
...
Documentation/i2c/instantiating-devices Method 1c: Declare the I2C devices via ACPI · line 91
Quoted 13 lines
Documentation/i2c/instantiating-devices +1
-1@@ -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
For this I2C part:
Re: [PATCH 10/10] docs: fix broken documentation links
In reply to Mauro Carvalho ChehabQuoted 4 lines · Mauro Carvalho Chehab
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 <[email protected]>
Thanks, didn't notice that.
Quoted 1 line
Documentation/i2c/instantiating-devices | 2 +-
...
Documentation/i2c/instantiating-devices Method 1c: Declare the I2C devices via ACPI · line 91
Quoted 13 lines
Documentation/i2c/instantiating-devices +1
-1@@ -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
For this I2C part:
_______________________________________________
Virtualization mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
Re: [PATCH 10/10] docs: fix broken documentation links
In reply to Mauro Carvalho ChehabQuoted 4 lines · Mauro Carvalho Chehab
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 <[email protected]>
Thanks, didn't notice that.
Quoted 1 line
Documentation/i2c/instantiating-devices | 2 +-
...
Documentation/i2c/instantiating-devices Method 1c: Declare the I2C devices via ACPI · line 91
Quoted 13 lines
Documentation/i2c/instantiating-devices +1
-1@@ -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
For this I2C part:
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Federico Vaga
maintainerRe: [PATCH 10/10] docs: fix broken documentation links
In reply to Mauro Carvalho ChehabQuoted 73 lines · CEST Mauro Carvalho Chehab
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 <[email protected]>--- Documentation/acpi/dsd/leds.txt | 2 +- Documentation/admin-guide/kernel-parameters.rst | 6 +++--- Documentation/admin-guide/kernel-parameters.txt | 16 ++++++++-------- Documentation/admin-guide/ras.rst | 2 +- .../devicetree/bindings/net/fsl-enetc.txt | 7 +++---- .../bindings/pci/amlogic,meson-pcie.txt | 2 +- .../bindings/regulator/qcom,rpmh-regulator.txt | 2 +- Documentation/devicetree/booting-without-of.txt | 2 +- Documentation/driver-api/gpio/board.rst | 2 +- Documentation/driver-api/gpio/consumer.rst | 2 +- .../firmware-guide/acpi/enumeration.rst | 2 +- .../firmware-guide/acpi/method-tracing.rst | 2 +- Documentation/i2c/instantiating-devices | 2 +- Documentation/sysctl/kernel.txt | 4 ++-- .../translations/it_IT/process/4.Coding.rst | 2 +- .../translations/it_IT/process/howto.rst | 2 +- .../it_IT/process/stable-kernel-rules.rst | 4 ++-- .../translations/zh_CN/process/4.Coding.rst | 2 +- Documentation/x86/x86_64/5level-paging.rst | 2 +- Documentation/x86/x86_64/boot-options.rst | 4 ++-- .../x86/x86_64/fake-numa-for-cpusets.rst | 2 +- MAINTAINERS | 6 +++--- arch/arm/Kconfig | 2 +- arch/arm64/kernel/kexec_image.c | 2 +- arch/powerpc/Kconfig | 2 +- arch/x86/Kconfig | 16 ++++++++-------- arch/x86/Kconfig.debug | 2 +- arch/x86/boot/header.S | 2 +- arch/x86/entry/entry_64.S | 2 +- arch/x86/include/asm/bootparam_utils.h | 2 +- arch/x86/include/asm/page_64_types.h | 2 +- arch/x86/include/asm/pgtable_64_types.h | 2 +- arch/x86/kernel/cpu/microcode/amd.c | 2 +- arch/x86/kernel/kexec-bzimage64.c | 2 +- arch/x86/kernel/pci-dma.c | 2 +- arch/x86/mm/tlb.c | 2 +- arch/x86/platform/pvh/enlighten.c | 2 +- drivers/acpi/Kconfig | 10 +++++----- drivers/net/ethernet/faraday/ftgmac100.c | 2 +- .../fieldbus/Documentation/fieldbus_dev.txt | 4 ++-- drivers/vhost/vhost.c | 2 +- include/acpi/acpi_drivers.h | 2 +- include/linux/fs_context.h | 2 +- include/linux/lsm_hooks.h | 2 +- mm/Kconfig | 2 +- security/Kconfig | 2 +- tools/include/linux/err.h | 2 +- tools/objtool/Documentation/stack-validation.txt | 4 ++-- tools/testing/selftests/x86/protection_keys.c | 2 +- 49 files changed, 78 insertions(+), 79 deletions(-)(quoted diff) +0
-0
b/Documentation/acpi/dsd/leds.txtindex81a63af42ed2..cc58b1a574c5100644Documentation/acpi/dsd/leds.txt +0
-0@@ -96,4 +96,4 @@ where<URL:http://www.uefi.org/sites/default/files/resources/_DSD-hierarchical-da ta-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(quoted diff) +0
-0
b/Documentation/admin-guide/kernel-parameters.rstindex0124980dca2d..8d3273e32eb1100644
Documentation/admin-guide/kernel-parameters.rst parameter is applicable:: · line 170
Quoted 4 lines
Documentation/admin-guide/kernel-parameters.rst +0
-1@@ -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
.
Quoted 23 lines
Documentation/admin-guide/kernel-parameters.rst +1
-0+ 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 theoption:: 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 extremeDocumentation/admin-guide/kernel-parameters.rst +2
-2-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(quoted diff) +0
-0
b/Documentation/admin-guide/kernel-parameters.txtindex138f6664b2e2..bc5f202d42ec100644
Documentation/admin-guide/kernel-parameters.txt line 55
Quoted 3 lines
Documentation/admin-guide/kernel-parameters.txt +0
-0@@ -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/admin-guide/kernel-parameters.txt line 56
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +0
-1- Documentation/acpi/debug.txt for more
information about
Documentation/admin-guide/kernel-parameters.txt line 56
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +1
-0+ Documentation/firmware-guide/acpi/debug.rst
for more information about
Documentation/admin-guide/kernel-parameters.txt line 965
Quoted 7 lines
Documentation/admin-guide/kernel-parameters.txt +0
-0debug layers and levels. Enable processor driver info messages:@@ -963,7 +963,7 @@ for details. nompx [X86] Disables Intel Memory Protection
Extensions.
Documentation/admin-guide/kernel-parameters.txt line 966
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +0
-1- See Documentation/x86/intel_mpx.txt for
more
Documentation/admin-guide/kernel-parameters.txt line 966
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +1
-0+ See Documentation/x86/intel_mpx.rst for
more
Documentation/admin-guide/kernel-parameters.txt
Quoted 3 lines
Documentation/admin-guide/kernel-parameters.txt +0
-0information about the feature. nopku [X86] Disable Memory Protection Keys CPU
feature found
Documentation/admin-guide/kernel-parameters.txt line 1189
Quoted 2 lines
Documentation/admin-guide/kernel-parameters.txt +0
-0@@ -1189,7 +1189,7 @@ that is to be dynamically loaded by Linux.
If there are
Documentation/admin-guide/kernel-parameters.txt line 1190
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +0
-0multiple variables with the same name but
with different
Documentation/admin-guide/kernel-parameters.txt line 1191
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +0
-0vendor GUIDs, all of them will be loaded.
See
Documentation/admin-guide/kernel-parameters.txt line 1192
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +0
-1- Documentation/acpi/ssdt-overlays.txt for
details.
Documentation/admin-guide/kernel-parameters.txt line 1192
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +1
-0+ Documentation/admin-guide/acpi/ssdt-
overlays.rst for details.
Documentation/admin-guide/kernel-parameters.txt line 2386
Quoted 8 lines
Documentation/admin-guide/kernel-parameters.txt +0
-1eisa_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
Documentation/admin-guide/kernel-parameters.txt line 2386
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +1
-0+ mce=option [X86-64] See Documentation/x86/x86_64/boot-
options.rst
Documentation/admin-guide/kernel-parameters.txt line 2440
Quoted 6 lines
Documentation/admin-guide/kernel-parameters.txt +0
-0md= [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
Documentation/admin-guide/kernel-parameters.txt
Quoted 3 lines
Documentation/admin-guide/kernel-parameters.txt +1
-1option. - See Documentation/memory-hotplug.txt. + See Documentation/admin-guide/mm/memory-
hotplug.rst.
Documentation/admin-guide/kernel-parameters.txt line 2528
Quoted 5 lines
Documentation/admin-guide/kernel-parameters.txt +0
-0memmap=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
Documentation/admin-guide/kernel-parameters.txt
Quoted 3 lines
Documentation/admin-guide/kernel-parameters.txt +0
-1mem_encrypt=off: Do not activate SME - Refer to Documentation/x86/amd-memory-
encryption.txt
Documentation/admin-guide/kernel-parameters.txt line 2531
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +1
-0+ Refer to Documentation/x86/amd-memory-
encryption.rst
Documentation/admin-guide/kernel-parameters.txt line 2532
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +0
-0for details on when memory encryption can
be activated.
Documentation/admin-guide/kernel-parameters.txt line 5054
Quoted 13 lines
Documentation/admin-guide/kernel-parameters.txt +1
-1mem_sleep_default= [SUSPEND] Default system suspend mode:@@ -3528,7 +3528,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 }@@ -5054,7 +5054,7 @@ Can be used multiple times for multiple
devices.
Documentation/admin-guide/kernel-parameters.txt line 5055
Quoted 2 lines
Documentation/admin-guide/kernel-parameters.txt +0
-0vga= [BOOT,X86-32] Select a particular video
mode
Documentation/admin-guide/kernel-parameters.txt
Quoted 5 lines
Documentation/admin-guide/kernel-parameters.txt +1
-1- 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
Quoted 60 lines
(quoted diff) +0
-0
b/Documentation/admin-guide/ras.rstindexc7495e42e6f4..2b20f5f7380d100644Documentation/admin-guide/ras.rst +1
-1@@ -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 *************************************(quoted diff) +0
-0
b/Documentation/devicetree/bindings/net/fsl-enetc.txtindexc812e25ae90f..25fc687419db100644Documentation/devicetree/bindings/net/fsl-enetc.txt +3
-4@@ -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:(quoted diff) +0
-0
b/Documentation/devicetree/bindings/pci/amlogic,meson-pcie.txtindex12b18f82d441..efa2c8b9b85a100644Documentation/devicetree/bindings/pci/amlogic,meson-pcie.txt +0
-0@@ -3,7 +3,7 @@ Amlogic Meson AXG DWC PCIE SoC controller Amlogic Meson PCIe host controller is based on the Synopsys DesignWare PCIcore. It shares common functions with the PCIe DesignWare core driver and inherits common properties defined in
Documentation/devicetree/bindings/pci/amlogic,meson-pcie.txt +1
-1-Documentation/devicetree/bindings/pci/designware-pci.txt. +Documentation/devicetree/bindings/pci/designware-pcie.txt. Additional properties are described here:diff --git
a/Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txtb/Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txtindex7ef2dbe48e8a..14d2eee96b3d100644
Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txt Second Level Nodes - Regulators · line 97
Quoted 1 line
Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txt +0
-0@@ -97,7 +97,7 @@ Second Level Nodes - Regulators sent for this regulator including those which are
for a
Quoted 126 lines
Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txt +1
-1strictly lower power state. -Other properties defined in Documentation/devicetree/bindings/regulator.txt +Other properties defined in
Documentation/devicetree/bindings/regulator/regulator.txtmay 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 diff --gita/Documentation/devicetree/booting-without-of.txtb/Documentation/devicetree/booting-without-of.txtindexe86bd2f64117..60f8640f2b2f100644Documentation/devicetree/booting-without-of.txt +1
-1@@ -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(quoted diff) +0
-0
b/Documentation/driver-api/gpio/board.rstindexb37f3f7b8926..ce91518bf9f4100644Documentation/driver-api/gpio/board.rst +1
-1@@ -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 -------------(quoted diff) +0
-0
b/Documentation/driver-api/gpio/consumer.rstindex5e4d8aa68913..fdecb6d711db100644Documentation/driver-api/gpio/consumer.rst +0
-0@@ -437,7 +437,7 @@ case, it will be handled by the GPIO subsystemautomatically. However, if the
_DSDis not present, the mappings between GpioIo()/GpioInt() resources and GPIO connection IDs need to be provided by device drivers.Documentation/driver-api/gpio/consumer.rst +1
-1-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(quoted diff) +0
-0
b/Documentation/firmware-guide/acpi/enumeration.rstindex6b32b7be8c85..65f5bb5725ac100644Documentation/firmware-guide/acpi/enumeration.rst +1
-1@@ -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 moreinformation about the
_DSDbinding related to GPIOs.MFD devices
(quoted diff) +0
-0
b/Documentation/firmware-guide/acpi/method-tracing.rstindexd0b077b73f5f..0aa7e2c5d32a100644Documentation/firmware-guide/acpi/method-tracing.rst +0
-0@@ -68,7 +68,7 @@ c. Filter out the debug layer/level matched logs when thespecified
Where:
0xXXXXXXXX/0xYYYYYYYYDocumentation/firmware-guide/acpi/method-tracing.rst +1
-1- Refer to Documentation/acpi/debug.txt for possible debug layer/level + Refer to Documentation/firmware-guide/acpi/debug.rst for possibledebug layer/level masking values.
\PPPP.AAAA.TTTT.HHHH
Full path of a control method that can be found in the ACPI namespace.(quoted diff) +0
-0b/Documentation/i2c/instantiating-devices index
0d85ac1935b7..5a3e2f331e8c100644Documentation/i2c/instantiating-devices +0
-1@@ -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. +whichis currently located at
Documentation/firmware-guide/acpi/enumeration.rst.Method 2: Instantiate the devices explicitly
(quoted diff) +0
-0
b/Documentation/sysctl/kernel.txtindexf0c86fbb3b48..92f7f34b021a100644Documentation/sysctl/kernel.txt +0
-0@@ -155,7 +155,7 @@ is 0x15 and the full version number is 0x234, this filewill contain the value 340 =
0x154.See the
type_of_loaderandext_loader_typefields inDocumentation/sysctl/kernel.txt +1
-1-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 exampleabove, this file will contain the value 564 =
0x234.See the
type_of_loaderandext_loader_verfields inDocumentation/sysctl/kernel.txt +1
-1-Documentation/x86/boot.txt for additional information. +Documentation/x86/boot.rst for additional information. ==============================================================(quoted diff) +0
-0
b/Documentation/translations/it_IT/process/4.Coding.rstindexc05b89e616dd..1d23e951491f100644Documentation/translations/it_IT/process/4.Coding.rst +0
-0@@ -370,7 +370,7 @@ con cosa stanno lavorando. Consultate:
Documentation/ABI/READMEper avere una descrizione di come questi documenti devono essere impostati e quali informazioni devono essere fornite.
Quoted 6 lines
-Il file :ref:
Documentation/translations/it_IT/admin-guide/kernel-parameters.rst <kernelparameters>+Il file :ref:Documentation/admin-guide/kernel-parameters.rst <kernelparameters>descrive tutti i parametri di avvio del kernel. Ogni patch che aggiunga nuovi parametri dovrebbe aggiungere nuove voci a questo file.
ACK
I will provide later a patch that adds that translation (just the .rst file)
Quoted 10 lines
(quoted diff) +0
-0
b/Documentation/translations/it_IT/process/howto.rstindex9903ac7c566b..44e6077730e8100644Documentation/translations/it_IT/process/howto.rst +0
-0@@ -131,7 +131,7 @@ Di seguito una lista di file che sono presenti neisorgente del kernel e che "Linux kernel patch submission format"
Documentation/translations/it_IT/process/howto.rst +0
-1http://linux.yyz.us/patch-format.html - :ref:`Documentation/process/translations/it_IT/stable-api-nonsense.rst
Quoted 3 lines
<
it_stable_api_nonsense>+ :ref:Documentation/translations/it_IT/process/stable-api-nonsense.rst<it_stable_api_nonsense>`
ACK
Quoted 8 lines
Questo file descrive la motivazioni sottostanti la conscia decisione di
non avere un API stabile all'interno del kernel, incluso cose come: diff --gita/Documentation/translations/it_IT/process/stable-kernel-rules.rstb/Documentation/translations/it_IT/process/stable-kernel-rules.rstindex48e88e5ad2c5..4f206cee31a7100644Documentation/translations/it_IT/process/stable-kernel-rules.rst +0
-0@@ -33,7 +33,7 @@ Regole sul tipo di patch che vengono o non vengono
Quoted 8 lines
accettate nei sorgenti - Non deve includere alcuna correzione "banale" (correzioni grammaticali, pulizia dagli spazi bianchi, eccetera).
- Deve rispettare le regole scritte in
- :ref:`Documentation/translation/it_IT/process/submitting-patches.rst
<it_submittingpatches>+ :ref:Documentation/translations/it_IT/process/submitting-patches.rst<it_submittingpatches>` - Questa patch o una equivalente deve esistere già nei sorgenti principali di Linux
ACK
Quoted 11 lines
Documentation/translations/it_IT/process/stable-kernel-rules.rst +0
-0@@ -43,7 +43,7 @@ Procedura per sottomettere patch per i sorgenti -stable - Se la patch contiene modifiche a dei file nelle cartelle net/ o
drivers/net, allora seguite le linee guida descritte in
- :ref:`Documentation/translation/it_IT/networking/netdev-FAQ.rst
<it_netdev-FAQ>; + :ref:Documentation/translations/it_IT/networking/netdev-FAQ.rst<it_netdev-FAQ>`; ma solo dopo aver verificato al seguente indirizzo che la patch non sia già in coda:
ACK
Thanks for the fixes, out of curiosity. How did you spot those mistakes?
Quoted 106 lines
https://patchwork.ozlabs.org/bundle/davem/stable/?series=&submitter=&state=
*&q=&archive= diff --gita/Documentation/translations/zh_CN/process/4.Coding.rstb/Documentation/translations/zh_CN/process/4.Coding.rstindex5301e9d55255..8bb777941394100644Documentation/translations/zh_CN/process/4.Coding.rst +1
-1@@ -241,7 +241,7 @@ scripts/coccinelle目录下已经打包了相当多的内核“语义补丁” 任何添加新用户空间界面的代码(包括新的sysfs或/proc文件)都应该包含该界面的 文档,该文档使用户空间开发人员能够知道他们在使用什么。请参阅 -Documentation/abi/readme,了解如何格式化此文档以及需要提供哪些信息。 +Documentation/ABI/README,了解如何格式化此文档以及需要提供哪些信息。 文件 :ref:`Documentation/admin-guide/kernel-parameters.rst<kernelparameters>` 描述了内核的所有引导时间参数。任何添加新参数的补丁都应该向该文件添加适当的
(quoted diff) +0
-0
b/Documentation/x86/x86_64/5level-paging.rstindexab88a4514163..44856417e6a5100644Documentation/x86/x86_64/5level-paging.rst +0
-0@@ -20,7 +20,7 @@ physical address space. This "ought to be enough foranybody" ©. QEMU 2.9 and later support 5-level paging.
Virtual memory layout for 5-level paging is described in
Documentation/x86/x86_64/5level-paging.rst +1
-1-Documentation/x86/x86_64/mm.txt +Documentation/x86/x86_64/mm.rst Enabling 5-level paging(quoted diff) +0
-0
b/Documentation/x86/x86_64/boot-options.rstindex2f69836b8445..6a4285a3c7a4100644Documentation/x86/x86_64/boot-options.rst +0
-1@@ -9,7 +9,7 @@ only the AMD64 specific ones are listed here. Machine check ============= -Please see Documentation/x86/x86_64/machinecheck for sysfs runtimetunables. +Please see
Documentation/x86/x86_64/machinecheck.rstfor sysfs runtime tunables.mce=off
Documentation/x86/x86_64/boot-options.rst +1
-1Disable 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(quoted diff) +0
-0
b/Documentation/x86/x86_64/fake-numa-for-cpusets.rstindex74fbb78b3c67..04df57b9aa3f100644Documentation/x86/x86_64/fake-numa-for-cpusets.rst +0
-0@@ -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, seeDocumentation/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 diff --git a/MAINTAINERS b/MAINTAINERS
index0c84bf76d165..47aa4f6defb9100644MAINTAINERS +0
-0@@ -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.txtMAINTAINERS +3
-3-F: Documentation/hwmon/lochnagar +F: Documentation/hwmon/lochnagar.rst CISCO FCOE HBA DRIVER M: Satish Kharat <[email protected]>@@ -11272,7 +11272,7 @@ NXP FXAS21002C DRIVER M: Rui Miguel Silva <[email protected]> L: [email protected] 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@@ -13043,7 +13043,7 @@ M: Niklas Cassel <[email protected]> L: [email protected] S: Maintained F: drivers/net/ethernet/stmicro/stmmac/dwmac-qcom-ethqos.c -F: Documentation/devicetree/bindings/net/qcom,dwmac.txt +F: Documentation/devicetree/bindings/net/qcom,ethqos.txt QUALCOMM GENERIC INTERFACE I2C DRIVER M: Alok Chauhan <[email protected]>arch/arm/Kconfig +0
-0
arch/arm/Kconfig config SMP · line 1267
Quoted 6 lines
arch/arm/Kconfig +1
-1@@ -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
arch/arm64/kernel/kexec_image.c static void *image_load(struct kimage *image, · line 56
Quoted 12 lines
<http://tldp.org/HOWTO/SMP-HOWTO.html>.
(quoted diff) +0
-0
b/arch/arm64/kernel/kexec_image.cindex07bf740bea91..31cc2f423aa8100644arch/arm64/kernel/kexec_image.c +1
-1@@ -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
arch/powerpc/Kconfig config PPC_MEM_KEYS · line 898
Quoted 9 lines
arch/arm64/kernel/kexec_image.c +0
-0* is non-zero (practically speaking, since v3.17). */ h = (struct arm64_image_header *)kernel;arch/powerpc/Kconfig +0
-0@@ -898,7 +898,7 @@ config PPC_MEM_KEYS page-based protections, but without requiring modification of
the
arch/x86/Kconfig config SMP · line 395
Quoted 13 lines
arch/powerpc/Kconfig +1
-1page tables when an application changes protection domains. - For details, see Documentation/vm/protection-keys.rst + For details, see Documentation/x86/protection-keys.rst If unsure, say y.arch/x86/Kconfig +0
-0@@ -395,7 +395,7 @@ config SMP Y to "Enhanced Real Time Clock Support", below. The "Advanced
Power
arch/x86/Kconfig config SMP
Quoted 5 lines
arch/x86/Kconfig +1
-1Management" 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
Quoted 7 lines
<http://www.tldp.org/docs.html#howto>.
arch/x86/Kconfig +0
-0@@ -1290,7 +1290,7 @@ config MICROCODE the Linux kernel. The preferred method to load microcode from a detached initrd isdescribed - in
Documentation/x86/microcode.txt. For that you
need to
arch/x86/Kconfig config MICROCODE_OLD_INTERFACE · line 1330
Quoted 7 lines
enable + in
Documentation/x86/microcode.rst. For that you need to enableCONFIG_BLK_DEV_INITRDin order for the loader to be able to scan the initrd for microcode blobs.arch/x86/Kconfig +0
-0@@ -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
arch/x86/Kconfig config MICROCODE_OLD_INTERFACE · line 1331
Quoted 1 line
arch/x86/Kconfig +0
-0should've switched to the early loading method with the initrd
or
Quoted 24 lines
arch/x86/Kconfig +3
-3- 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 moreinformation. If you are unsure how to answer this question, answer N.
config
ARCH_PROC_KCORE_TEXT
arch/x86/Kconfig config MTRR · line 1783
Quoted 1 line
arch/x86/Kconfig +0
-0@@ -1783,7 +1783,7 @@ config MTRR You can safely say Y even if your machine doesn't have MTRRs,
you'll
Quoted 17 lines
arch/x86/Kconfig +2
-2just 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.
arch/x86/Kconfig config X86_INTEL_MEMORY_PROTECTION_KEYS · line 1911
Quoted 1 line
arch/x86/Kconfig +0
-0@@ -1911,7 +1911,7 @@ config X86_INTEL_MEMORY_PROTECTION_KEYS page-based protections, but without requiring modification of
the
arch/x86/boot/header.S start_sys_seg: .word SYSSEG
Quoted 25 lines
arch/x86/Kconfig +1
-1page tables when an application changes protection domains. - For details, see Documentation/x86/protection-keys.txt + For details, see Documentation/x86/protection-keys.rst If unsure, say y.arch/x86/Kconfig.debug +1
-1@@ -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_LEAKarch/x86/boot/header.S +0
-0@@ -313,7 +313,7 @@ start_sys_seg: .word SYSSEG
# obsolete and meaningless,
Quoted 3 lines
but just
type_of_loader: .byte 0 # 0 means ancient
bootloader, newer
Quoted 1 line
# bootloaders know
to change this.
arch/x86/boot/header.S
Quoted 1 line
arch/x86/boot/header.S +0
-1- # See
Documentation/x86/boot.txt for
arch/x86/boot/header.S
Quoted 1 line
arch/x86/boot/header.S +1
-0+ # See
Documentation/x86/boot.rst for
Quoted 78 lines
arch/x86/boot/header.S +0
-0# assigned ids # flags, unused bits must be zero (RFU) bit within loadflagsarch/x86/entry/entry_64.S +1
-1@@ -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(quoted diff) +0
-0
b/arch/x86/include/asm/bootparam_utils.hindexf6f6ef436599..101eb944f13c100644arch/x86/include/asm/bootparam_utils.h +1
-1@@ -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.(quoted diff) +0
-0
b/arch/x86/include/asm/page_64_types.hindex793c14c372cb..288b065955b7100644arch/x86/include/asm/page_64_types.h +0
-1@@ -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 memorymap. */
#define
__PHYSICAL_MASK_SHIFT52(quoted diff) +0
-0
b/arch/x86/include/asm/pgtable_64_types.hindex88bca456da99..52e5f5f2240d100644arch/x86/include/asm/pgtable_64_types.h +1
-1@@ -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(quoted diff) +0
-0
b/arch/x86/kernel/cpu/microcode/amd.cindexe1f3ba19ba54..06d4e67f31ab100644arch/x86/kernel/cpu/microcode/amd.c +1
-1@@ -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" ;(quoted diff) +0
-0
b/arch/x86/kernel/kexec-bzimage64.cindex22f60dd26460..b07e7069b09e100644
arch/x86/kernel/kexec-bzimage64.c static void *bzImage64_load(struct kimage *image, char · line 419
Quoted 4 lines
arch/x86/kernel/kexec-bzimage64.c +0
-1@@ -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
*/
Quoted 35 lines
arch/x86/kernel/kexec-bzimage64.c +1
-0+/* 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? */ arch/x86/kernel/pci-dma.c +1
-1@@ -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)arch/x86/mm/tlb.c +1
-1@@ -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 (quoted diff) +0
-0
b/arch/x86/platform/pvh/enlighten.cindex1861a2ba0f2b..c0a502f7e3a7100644
arch/x86/platform/pvh/enlighten.c static void __init init_pvh_bootparams(bool xen_guest) · line 91
Quoted 7 lines
arch/x86/platform/pvh/enlighten.c +1
-1@@ -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
drivers/acpi/Kconfig config ACPI_CUSTOM_DSDT_FILE · line 335
Quoted 9 lines
arch/x86/platform/pvh/enlighten.c +0
-0* environment (i.e. hardware_subarch 0). drivers/acpi/Kconfig +0
-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.
drivers/acpi/Kconfig config ACPI_TABLE_UPGRADE · line 355
Quoted 7 lines
drivers/acpi/Kconfig +1
-1- 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
drivers/acpi/Kconfig config ACPI_TABLE_UPGRADE · line 356
Quoted 1 line
drivers/acpi/Kconfig +0
-0via initrd. No functional change if no ACPI tables are passed
via
drivers/acpi/Kconfig config ACPI_TABLE_UPGRADE
Quoted 3 lines
drivers/acpi/Kconfig +1
-1initrd, 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
drivers/acpi/Kconfig config ACPI_TABLE_OVERRIDE_VIA_BUILTIN_INITRD · line 365
Quoted 5 lines
drivers/acpi/Kconfig +0
-0config 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
drivers/acpi/Kconfig config ACPI_TABLE_OVERRIDE_VIA_BUILTIN_INITRD
Quoted 4 lines
drivers/acpi/Kconfig +1
-1from built-in uncompressed initrd. - See Documentation/acpi/initrd_table_override.txt for details + See Documentation/admin-guide/acpi/initrd_table_override.rst for
details
drivers/acpi/Kconfig config ACPI_DEBUG · line 376
Quoted 7 lines
drivers/acpi/Kconfig +0
-0config 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
drivers/acpi/Kconfig config ACPI_DEBUG · line 377
Quoted 2 lines
drivers/acpi/Kconfig +1
-1- parameters documented in Documentation/acpi/debug.txt and + parameters documented in Documentation/firmware-guide/acpi/
debug.rst and
drivers/acpi/Kconfig config ACPI_CUSTOM_METHOD · line 446
Quoted 6 lines
Documentation/admin-guide/kernel-parameters.rstto control the type and amount of debug output.drivers/acpi/Kconfig +0
-0@@ -445,7 +445,7 @@ config ACPI_CUSTOM_METHOD help This debug facility allows ACPI AML methods to be inserted and/
or
drivers/acpi/Kconfig config ACPI_CUSTOM_METHOD
Quoted 5 lines
drivers/acpi/Kconfig +1
-1replaced 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
drivers/acpi/Kconfig config ACPI_CUSTOM_METHOD · line 451
Quoted 1 line
drivers/acpi/Kconfig +0
-0kernel memory to be written to by root (uid=0) users, allowing
them
Quoted 75 lines
(quoted diff) +0
-0
b/drivers/net/ethernet/faraday/ftgmac100.cindexb17b79e612a3..ac6280ad43a1100644drivers/net/ethernet/faraday/ftgmac100.c +1
-1@@ -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);(quoted diff) +0
-0
b/drivers/staging/fieldbus/Documentation/fieldbus_dev.txtindex56af3f650fa3..89fb8e14676f100644drivers/staging/fieldbus/Documentation/fieldbus_dev.txt +0
-0@@ -54,8 +54,8 @@ a limited few common behaviours and properties. Thisallows us to define a simple interface consisting of a character device and a set of sysfs files:
See:
drivers/staging/fieldbus/Documentation/fieldbus_dev.txt +2
-2-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 gettheir diff --git
a/drivers/vhost/vhost.cb/drivers/vhost/vhost.cindex1e3ed41ae1f3..69938dbae2d0100644drivers/vhost/vhost.c +1
-1@@ -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) {include/acpi/acpi_drivers.h +1
-1@@ -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.
*/
#defineACPI_BUS_COMPONENT0x00010000include/linux/fs_context.h +0
-0@@ -85,7 +85,7 @@ struct fs_parameter {* Superblock creation fills in ->root whereas reconfiguration begins with this * already set.
*
- * SeeDocumentation/filesystems/mounting.txt
+ * SeeDocumentation/filesystems/mount_api.txt
*/
structfs_context{include/linux/fs_context.h +0
-0const struct fs_context_operations *ops;include/linux/lsm_hooks.h +0
-0
include/linux/lsm_hooks.h line 83
Quoted 8 lines
include/linux/lsm_hooks.h +1
-1@@ -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
mm/Kconfig config MEMORY_HOTPLUG_DEFAULT_ONLINE · line 165
Quoted 6 lines
mm/Kconfig +0
-0@@ -165,7 +165,7 @@ config MEMORY_HOTPLUG_DEFAULT_ONLINE onlining policy (/sys/devices/system/memory/auto_online_blocks)
which
mm/Kconfig config MEMORY_HOTPLUG_DEFAULT_ONLINE · line 166
Quoted 1 line
mm/Kconfig +0
-0determines what happens to newly added memory regions. Policy
setting
Quoted 6 lines
mm/Kconfig +1
-1can always be changed at runtime. - See Documentation/memory-hotplug.txt for more information. + See Documentation/admin-guide/mm/memory-hotplug.rst for moreinformation.
Say Y here if you want all hot-plugged memory blocks to appear
in
Quoted 64 lines
mm/Kconfig +0
-0'online' state by default.security/Kconfig +1
-1@@ -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"tools/include/linux/err.h +1
-1@@ -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(quoted diff) +0
-0
b/tools/objtool/Documentation/stack-validation.txtindex4dd11a554b9b..de094670050b100644tools/objtool/Documentation/stack-validation.txt +0
-0@@ -21,7 +21,7 @@ instructions). Similarly, it knows how to follow switchstatements, for which gcc sometimes uses jump tables.
(Objtool also has an 'orc generate' subcommand which generates debuginfo
tools/objtool/Documentation/stack-validation.txt +2
-2-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(quoted diff) +0
-0
b/tools/testing/selftests/x86/protection_keys.cindex5d546dcdbc80..798a5ddeee55100644tools/testing/selftests/x86/protection_keys.c +0
-1@@ -1,6 +1,6 @@// SPDX-License-Identifier: GPL-2.0 /* -* Tests x86 Memory Protection Keys (see
Documentation/x86/protection-keys.txt) + * Tests x86 Memory Protection Keys (seeDocumentation/x86/protection-keys.rst) *
* There are examples in here of:
* * how to set protection keys on memory
Federico Vaga
maintainerRe: [PATCH 10/10] docs: fix broken documentation links
In reply to Mauro Carvalho ChehabQuoted 73 lines · CEST Mauro Carvalho Chehab
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 <[email protected]>--- Documentation/acpi/dsd/leds.txt | 2 +- Documentation/admin-guide/kernel-parameters.rst | 6 +++--- Documentation/admin-guide/kernel-parameters.txt | 16 ++++++++-------- Documentation/admin-guide/ras.rst | 2 +- .../devicetree/bindings/net/fsl-enetc.txt | 7 +++---- .../bindings/pci/amlogic,meson-pcie.txt | 2 +- .../bindings/regulator/qcom,rpmh-regulator.txt | 2 +- Documentation/devicetree/booting-without-of.txt | 2 +- Documentation/driver-api/gpio/board.rst | 2 +- Documentation/driver-api/gpio/consumer.rst | 2 +- .../firmware-guide/acpi/enumeration.rst | 2 +- .../firmware-guide/acpi/method-tracing.rst | 2 +- Documentation/i2c/instantiating-devices | 2 +- Documentation/sysctl/kernel.txt | 4 ++-- .../translations/it_IT/process/4.Coding.rst | 2 +- .../translations/it_IT/process/howto.rst | 2 +- .../it_IT/process/stable-kernel-rules.rst | 4 ++-- .../translations/zh_CN/process/4.Coding.rst | 2 +- Documentation/x86/x86_64/5level-paging.rst | 2 +- Documentation/x86/x86_64/boot-options.rst | 4 ++-- .../x86/x86_64/fake-numa-for-cpusets.rst | 2 +- MAINTAINERS | 6 +++--- arch/arm/Kconfig | 2 +- arch/arm64/kernel/kexec_image.c | 2 +- arch/powerpc/Kconfig | 2 +- arch/x86/Kconfig | 16 ++++++++-------- arch/x86/Kconfig.debug | 2 +- arch/x86/boot/header.S | 2 +- arch/x86/entry/entry_64.S | 2 +- arch/x86/include/asm/bootparam_utils.h | 2 +- arch/x86/include/asm/page_64_types.h | 2 +- arch/x86/include/asm/pgtable_64_types.h | 2 +- arch/x86/kernel/cpu/microcode/amd.c | 2 +- arch/x86/kernel/kexec-bzimage64.c | 2 +- arch/x86/kernel/pci-dma.c | 2 +- arch/x86/mm/tlb.c | 2 +- arch/x86/platform/pvh/enlighten.c | 2 +- drivers/acpi/Kconfig | 10 +++++----- drivers/net/ethernet/faraday/ftgmac100.c | 2 +- .../fieldbus/Documentation/fieldbus_dev.txt | 4 ++-- drivers/vhost/vhost.c | 2 +- include/acpi/acpi_drivers.h | 2 +- include/linux/fs_context.h | 2 +- include/linux/lsm_hooks.h | 2 +- mm/Kconfig | 2 +- security/Kconfig | 2 +- tools/include/linux/err.h | 2 +- tools/objtool/Documentation/stack-validation.txt | 4 ++-- tools/testing/selftests/x86/protection_keys.c | 2 +- 49 files changed, 78 insertions(+), 79 deletions(-)(quoted diff) +0
-0
b/Documentation/acpi/dsd/leds.txtindex81a63af42ed2..cc58b1a574c5100644Documentation/acpi/dsd/leds.txt +0
-0@@ -96,4 +96,4 @@ where<URL:http://www.uefi.org/sites/default/files/resources/_DSD-hierarchical-da ta-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(quoted diff) +0
-0
b/Documentation/admin-guide/kernel-parameters.rstindex0124980dca2d..8d3273e32eb1100644
Documentation/admin-guide/kernel-parameters.rst parameter is applicable:: · line 170
Quoted 4 lines
Documentation/admin-guide/kernel-parameters.rst +0
-1@@ -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
.
Quoted 23 lines
Documentation/admin-guide/kernel-parameters.rst +1
-0+ 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 theoption:: 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 extremeDocumentation/admin-guide/kernel-parameters.rst +2
-2-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(quoted diff) +0
-0
b/Documentation/admin-guide/kernel-parameters.txtindex138f6664b2e2..bc5f202d42ec100644
Documentation/admin-guide/kernel-parameters.txt line 55
Quoted 3 lines
Documentation/admin-guide/kernel-parameters.txt +0
-0@@ -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/admin-guide/kernel-parameters.txt line 56
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +0
-1- Documentation/acpi/debug.txt for more
information about
Documentation/admin-guide/kernel-parameters.txt line 56
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +1
-0+ Documentation/firmware-guide/acpi/debug.rst
for more information about
Documentation/admin-guide/kernel-parameters.txt line 965
Quoted 7 lines
Documentation/admin-guide/kernel-parameters.txt +0
-0debug layers and levels. Enable processor driver info messages:@@ -963,7 +963,7 @@ for details. nompx [X86] Disables Intel Memory Protection
Extensions.
Documentation/admin-guide/kernel-parameters.txt line 966
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +0
-1- See Documentation/x86/intel_mpx.txt for
more
Documentation/admin-guide/kernel-parameters.txt line 966
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +1
-0+ See Documentation/x86/intel_mpx.rst for
more
Documentation/admin-guide/kernel-parameters.txt
Quoted 3 lines
Documentation/admin-guide/kernel-parameters.txt +0
-0information about the feature. nopku [X86] Disable Memory Protection Keys CPU
feature found
Documentation/admin-guide/kernel-parameters.txt line 1189
Quoted 2 lines
Documentation/admin-guide/kernel-parameters.txt +0
-0@@ -1189,7 +1189,7 @@ that is to be dynamically loaded by Linux.
If there are
Documentation/admin-guide/kernel-parameters.txt line 1190
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +0
-0multiple variables with the same name but
with different
Documentation/admin-guide/kernel-parameters.txt line 1191
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +0
-0vendor GUIDs, all of them will be loaded.
See
Documentation/admin-guide/kernel-parameters.txt line 1192
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +0
-1- Documentation/acpi/ssdt-overlays.txt for
details.
Documentation/admin-guide/kernel-parameters.txt line 1192
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +1
-0+ Documentation/admin-guide/acpi/ssdt-
overlays.rst for details.
Documentation/admin-guide/kernel-parameters.txt line 2386
Quoted 8 lines
Documentation/admin-guide/kernel-parameters.txt +0
-1eisa_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
Documentation/admin-guide/kernel-parameters.txt line 2386
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +1
-0+ mce=option [X86-64] See Documentation/x86/x86_64/boot-
options.rst
Documentation/admin-guide/kernel-parameters.txt line 2440
Quoted 6 lines
Documentation/admin-guide/kernel-parameters.txt +0
-0md= [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
Documentation/admin-guide/kernel-parameters.txt
Quoted 3 lines
Documentation/admin-guide/kernel-parameters.txt +1
-1option. - See Documentation/memory-hotplug.txt. + See Documentation/admin-guide/mm/memory-
hotplug.rst.
Documentation/admin-guide/kernel-parameters.txt line 2528
Quoted 5 lines
Documentation/admin-guide/kernel-parameters.txt +0
-0memmap=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
Documentation/admin-guide/kernel-parameters.txt
Quoted 3 lines
Documentation/admin-guide/kernel-parameters.txt +0
-1mem_encrypt=off: Do not activate SME - Refer to Documentation/x86/amd-memory-
encryption.txt
Documentation/admin-guide/kernel-parameters.txt line 2531
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +1
-0+ Refer to Documentation/x86/amd-memory-
encryption.rst
Documentation/admin-guide/kernel-parameters.txt line 2532
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +0
-0for details on when memory encryption can
be activated.
Documentation/admin-guide/kernel-parameters.txt line 5054
Quoted 13 lines
Documentation/admin-guide/kernel-parameters.txt +1
-1mem_sleep_default= [SUSPEND] Default system suspend mode:@@ -3528,7 +3528,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 }@@ -5054,7 +5054,7 @@ Can be used multiple times for multiple
devices.
Documentation/admin-guide/kernel-parameters.txt line 5055
Quoted 2 lines
Documentation/admin-guide/kernel-parameters.txt +0
-0vga= [BOOT,X86-32] Select a particular video
mode
Documentation/admin-guide/kernel-parameters.txt
Quoted 5 lines
Documentation/admin-guide/kernel-parameters.txt +1
-1- 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
Quoted 60 lines
(quoted diff) +0
-0
b/Documentation/admin-guide/ras.rstindexc7495e42e6f4..2b20f5f7380d100644Documentation/admin-guide/ras.rst +1
-1@@ -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 *************************************(quoted diff) +0
-0
b/Documentation/devicetree/bindings/net/fsl-enetc.txtindexc812e25ae90f..25fc687419db100644Documentation/devicetree/bindings/net/fsl-enetc.txt +3
-4@@ -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:(quoted diff) +0
-0
b/Documentation/devicetree/bindings/pci/amlogic,meson-pcie.txtindex12b18f82d441..efa2c8b9b85a100644Documentation/devicetree/bindings/pci/amlogic,meson-pcie.txt +0
-0@@ -3,7 +3,7 @@ Amlogic Meson AXG DWC PCIE SoC controller Amlogic Meson PCIe host controller is based on the Synopsys DesignWare PCIcore. It shares common functions with the PCIe DesignWare core driver and inherits common properties defined in
Documentation/devicetree/bindings/pci/amlogic,meson-pcie.txt +1
-1-Documentation/devicetree/bindings/pci/designware-pci.txt. +Documentation/devicetree/bindings/pci/designware-pcie.txt. Additional properties are described here:diff --git
a/Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txtb/Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txtindex7ef2dbe48e8a..14d2eee96b3d100644
Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txt Second Level Nodes - Regulators · line 97
Quoted 1 line
Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txt +0
-0@@ -97,7 +97,7 @@ Second Level Nodes - Regulators sent for this regulator including those which are
for a
Quoted 126 lines
Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txt +1
-1strictly lower power state. -Other properties defined in Documentation/devicetree/bindings/regulator.txt +Other properties defined in
Documentation/devicetree/bindings/regulator/regulator.txtmay 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 diff --gita/Documentation/devicetree/booting-without-of.txtb/Documentation/devicetree/booting-without-of.txtindexe86bd2f64117..60f8640f2b2f100644Documentation/devicetree/booting-without-of.txt +1
-1@@ -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(quoted diff) +0
-0
b/Documentation/driver-api/gpio/board.rstindexb37f3f7b8926..ce91518bf9f4100644Documentation/driver-api/gpio/board.rst +1
-1@@ -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 -------------(quoted diff) +0
-0
b/Documentation/driver-api/gpio/consumer.rstindex5e4d8aa68913..fdecb6d711db100644Documentation/driver-api/gpio/consumer.rst +0
-0@@ -437,7 +437,7 @@ case, it will be handled by the GPIO subsystemautomatically. However, if the
_DSDis not present, the mappings between GpioIo()/GpioInt() resources and GPIO connection IDs need to be provided by device drivers.Documentation/driver-api/gpio/consumer.rst +1
-1-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(quoted diff) +0
-0
b/Documentation/firmware-guide/acpi/enumeration.rstindex6b32b7be8c85..65f5bb5725ac100644Documentation/firmware-guide/acpi/enumeration.rst +1
-1@@ -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 moreinformation about the
_DSDbinding related to GPIOs.MFD devices
(quoted diff) +0
-0
b/Documentation/firmware-guide/acpi/method-tracing.rstindexd0b077b73f5f..0aa7e2c5d32a100644Documentation/firmware-guide/acpi/method-tracing.rst +0
-0@@ -68,7 +68,7 @@ c. Filter out the debug layer/level matched logs when thespecified
Where:
0xXXXXXXXX/0xYYYYYYYYDocumentation/firmware-guide/acpi/method-tracing.rst +1
-1- Refer to Documentation/acpi/debug.txt for possible debug layer/level + Refer to Documentation/firmware-guide/acpi/debug.rst for possibledebug layer/level masking values.
\PPPP.AAAA.TTTT.HHHH
Full path of a control method that can be found in the ACPI namespace.(quoted diff) +0
-0b/Documentation/i2c/instantiating-devices index
0d85ac1935b7..5a3e2f331e8c100644Documentation/i2c/instantiating-devices +0
-1@@ -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. +whichis currently located at
Documentation/firmware-guide/acpi/enumeration.rst.Method 2: Instantiate the devices explicitly
(quoted diff) +0
-0
b/Documentation/sysctl/kernel.txtindexf0c86fbb3b48..92f7f34b021a100644Documentation/sysctl/kernel.txt +0
-0@@ -155,7 +155,7 @@ is 0x15 and the full version number is 0x234, this filewill contain the value 340 =
0x154.See the
type_of_loaderandext_loader_typefields inDocumentation/sysctl/kernel.txt +1
-1-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 exampleabove, this file will contain the value 564 =
0x234.See the
type_of_loaderandext_loader_verfields inDocumentation/sysctl/kernel.txt +1
-1-Documentation/x86/boot.txt for additional information. +Documentation/x86/boot.rst for additional information. ==============================================================(quoted diff) +0
-0
b/Documentation/translations/it_IT/process/4.Coding.rstindexc05b89e616dd..1d23e951491f100644Documentation/translations/it_IT/process/4.Coding.rst +0
-0@@ -370,7 +370,7 @@ con cosa stanno lavorando. Consultate:
Documentation/ABI/READMEper avere una descrizione di come questi documenti devono essere impostati e quali informazioni devono essere fornite.
Quoted 6 lines
-Il file :ref:
Documentation/translations/it_IT/admin-guide/kernel-parameters.rst <kernelparameters>+Il file :ref:Documentation/admin-guide/kernel-parameters.rst <kernelparameters>descrive tutti i parametri di avvio del kernel. Ogni patch che aggiunga nuovi parametri dovrebbe aggiungere nuove voci a questo file.
ACK
I will provide later a patch that adds that translation (just the .rst file)
Quoted 10 lines
(quoted diff) +0
-0
b/Documentation/translations/it_IT/process/howto.rstindex9903ac7c566b..44e6077730e8100644Documentation/translations/it_IT/process/howto.rst +0
-0@@ -131,7 +131,7 @@ Di seguito una lista di file che sono presenti neisorgente del kernel e che "Linux kernel patch submission format"
Documentation/translations/it_IT/process/howto.rst +0
-1http://linux.yyz.us/patch-format.html - :ref:`Documentation/process/translations/it_IT/stable-api-nonsense.rst
Quoted 3 lines
<
it_stable_api_nonsense>+ :ref:Documentation/translations/it_IT/process/stable-api-nonsense.rst<it_stable_api_nonsense>`
ACK
Quoted 8 lines
Questo file descrive la motivazioni sottostanti la conscia decisione di
non avere un API stabile all'interno del kernel, incluso cose come: diff --gita/Documentation/translations/it_IT/process/stable-kernel-rules.rstb/Documentation/translations/it_IT/process/stable-kernel-rules.rstindex48e88e5ad2c5..4f206cee31a7100644Documentation/translations/it_IT/process/stable-kernel-rules.rst +0
-0@@ -33,7 +33,7 @@ Regole sul tipo di patch che vengono o non vengono
Quoted 8 lines
accettate nei sorgenti - Non deve includere alcuna correzione "banale" (correzioni grammaticali, pulizia dagli spazi bianchi, eccetera).
- Deve rispettare le regole scritte in
- :ref:`Documentation/translation/it_IT/process/submitting-patches.rst
<it_submittingpatches>+ :ref:Documentation/translations/it_IT/process/submitting-patches.rst<it_submittingpatches>` - Questa patch o una equivalente deve esistere già nei sorgenti principali di Linux
ACK
Quoted 11 lines
Documentation/translations/it_IT/process/stable-kernel-rules.rst +0
-0@@ -43,7 +43,7 @@ Procedura per sottomettere patch per i sorgenti -stable - Se la patch contiene modifiche a dei file nelle cartelle net/ o
drivers/net, allora seguite le linee guida descritte in
- :ref:`Documentation/translation/it_IT/networking/netdev-FAQ.rst
<it_netdev-FAQ>; + :ref:Documentation/translations/it_IT/networking/netdev-FAQ.rst<it_netdev-FAQ>`; ma solo dopo aver verificato al seguente indirizzo che la patch non sia già in coda:
ACK
Thanks for the fixes, out of curiosity. How did you spot those mistakes?
Quoted 106 lines
https://patchwork.ozlabs.org/bundle/davem/stable/?series=&submitter=&state=
*&q=&archive= diff --gita/Documentation/translations/zh_CN/process/4.Coding.rstb/Documentation/translations/zh_CN/process/4.Coding.rstindex5301e9d55255..8bb777941394100644Documentation/translations/zh_CN/process/4.Coding.rst +1
-1@@ -241,7 +241,7 @@ scripts/coccinelle目录下已经打包了相当多的内核“语义补丁” 任何添加新用户空间界面的代码(包括新的sysfs或/proc文件)都应该包含该界面的 文档,该文档使用户空间开发人员能够知道他们在使用什么。请参阅 -Documentation/abi/readme,了解如何格式化此文档以及需要提供哪些信息。 +Documentation/ABI/README,了解如何格式化此文档以及需要提供哪些信息。 文件 :ref:`Documentation/admin-guide/kernel-parameters.rst<kernelparameters>` 描述了内核的所有引导时间参数。任何添加新参数的补丁都应该向该文件添加适当的
(quoted diff) +0
-0
b/Documentation/x86/x86_64/5level-paging.rstindexab88a4514163..44856417e6a5100644Documentation/x86/x86_64/5level-paging.rst +0
-0@@ -20,7 +20,7 @@ physical address space. This "ought to be enough foranybody" ©. QEMU 2.9 and later support 5-level paging.
Virtual memory layout for 5-level paging is described in
Documentation/x86/x86_64/5level-paging.rst +1
-1-Documentation/x86/x86_64/mm.txt +Documentation/x86/x86_64/mm.rst Enabling 5-level paging(quoted diff) +0
-0
b/Documentation/x86/x86_64/boot-options.rstindex2f69836b8445..6a4285a3c7a4100644Documentation/x86/x86_64/boot-options.rst +0
-1@@ -9,7 +9,7 @@ only the AMD64 specific ones are listed here. Machine check ============= -Please see Documentation/x86/x86_64/machinecheck for sysfs runtimetunables. +Please see
Documentation/x86/x86_64/machinecheck.rstfor sysfs runtime tunables.mce=off
Documentation/x86/x86_64/boot-options.rst +1
-1Disable 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(quoted diff) +0
-0
b/Documentation/x86/x86_64/fake-numa-for-cpusets.rstindex74fbb78b3c67..04df57b9aa3f100644Documentation/x86/x86_64/fake-numa-for-cpusets.rst +0
-0@@ -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, seeDocumentation/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 diff --git a/MAINTAINERS b/MAINTAINERS
index0c84bf76d165..47aa4f6defb9100644MAINTAINERS +0
-0@@ -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.txtMAINTAINERS +3
-3-F: Documentation/hwmon/lochnagar +F: Documentation/hwmon/lochnagar.rst CISCO FCOE HBA DRIVER M: Satish Kharat <[email protected]>@@ -11272,7 +11272,7 @@ NXP FXAS21002C DRIVER M: Rui Miguel Silva <[email protected]> L: [email protected] 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@@ -13043,7 +13043,7 @@ M: Niklas Cassel <[email protected]> L: [email protected] S: Maintained F: drivers/net/ethernet/stmicro/stmmac/dwmac-qcom-ethqos.c -F: Documentation/devicetree/bindings/net/qcom,dwmac.txt +F: Documentation/devicetree/bindings/net/qcom,ethqos.txt QUALCOMM GENERIC INTERFACE I2C DRIVER M: Alok Chauhan <[email protected]>arch/arm/Kconfig +0
-0
arch/arm/Kconfig config SMP · line 1267
Quoted 6 lines
arch/arm/Kconfig +1
-1@@ -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
arch/arm64/kernel/kexec_image.c static void *image_load(struct kimage *image, · line 56
Quoted 12 lines
<http://tldp.org/HOWTO/SMP-HOWTO.html>.
(quoted diff) +0
-0
b/arch/arm64/kernel/kexec_image.cindex07bf740bea91..31cc2f423aa8100644arch/arm64/kernel/kexec_image.c +1
-1@@ -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
arch/powerpc/Kconfig config PPC_MEM_KEYS · line 898
Quoted 9 lines
arch/arm64/kernel/kexec_image.c +0
-0* is non-zero (practically speaking, since v3.17). */ h = (struct arm64_image_header *)kernel;arch/powerpc/Kconfig +0
-0@@ -898,7 +898,7 @@ config PPC_MEM_KEYS page-based protections, but without requiring modification of
the
arch/x86/Kconfig config SMP · line 395
Quoted 13 lines
arch/powerpc/Kconfig +1
-1page tables when an application changes protection domains. - For details, see Documentation/vm/protection-keys.rst + For details, see Documentation/x86/protection-keys.rst If unsure, say y.arch/x86/Kconfig +0
-0@@ -395,7 +395,7 @@ config SMP Y to "Enhanced Real Time Clock Support", below. The "Advanced
Power
arch/x86/Kconfig config SMP
Quoted 5 lines
arch/x86/Kconfig +1
-1Management" 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
Quoted 7 lines
<http://www.tldp.org/docs.html#howto>.
arch/x86/Kconfig +0
-0@@ -1290,7 +1290,7 @@ config MICROCODE the Linux kernel. The preferred method to load microcode from a detached initrd isdescribed - in
Documentation/x86/microcode.txt. For that you
need to
arch/x86/Kconfig config MICROCODE_OLD_INTERFACE · line 1330
Quoted 7 lines
enable + in
Documentation/x86/microcode.rst. For that you need to enableCONFIG_BLK_DEV_INITRDin order for the loader to be able to scan the initrd for microcode blobs.arch/x86/Kconfig +0
-0@@ -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
arch/x86/Kconfig config MICROCODE_OLD_INTERFACE · line 1331
Quoted 1 line
arch/x86/Kconfig +0
-0should've switched to the early loading method with the initrd
or
Quoted 24 lines
arch/x86/Kconfig +3
-3- 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 moreinformation. If you are unsure how to answer this question, answer N.
config
ARCH_PROC_KCORE_TEXT
arch/x86/Kconfig config MTRR · line 1783
Quoted 1 line
arch/x86/Kconfig +0
-0@@ -1783,7 +1783,7 @@ config MTRR You can safely say Y even if your machine doesn't have MTRRs,
you'll
Quoted 17 lines
arch/x86/Kconfig +2
-2just 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.
arch/x86/Kconfig config X86_INTEL_MEMORY_PROTECTION_KEYS · line 1911
Quoted 1 line
arch/x86/Kconfig +0
-0@@ -1911,7 +1911,7 @@ config X86_INTEL_MEMORY_PROTECTION_KEYS page-based protections, but without requiring modification of
the
arch/x86/boot/header.S start_sys_seg: .word SYSSEG
Quoted 25 lines
arch/x86/Kconfig +1
-1page tables when an application changes protection domains. - For details, see Documentation/x86/protection-keys.txt + For details, see Documentation/x86/protection-keys.rst If unsure, say y.arch/x86/Kconfig.debug +1
-1@@ -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_LEAKarch/x86/boot/header.S +0
-0@@ -313,7 +313,7 @@ start_sys_seg: .word SYSSEG
# obsolete and meaningless,
Quoted 3 lines
but just
type_of_loader: .byte 0 # 0 means ancient
bootloader, newer
Quoted 1 line
# bootloaders know
to change this.
arch/x86/boot/header.S
Quoted 1 line
arch/x86/boot/header.S +0
-1- # See
Documentation/x86/boot.txt for
arch/x86/boot/header.S
Quoted 1 line
arch/x86/boot/header.S +1
-0+ # See
Documentation/x86/boot.rst for
Quoted 78 lines
arch/x86/boot/header.S +0
-0# assigned ids # flags, unused bits must be zero (RFU) bit within loadflagsarch/x86/entry/entry_64.S +1
-1@@ -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(quoted diff) +0
-0
b/arch/x86/include/asm/bootparam_utils.hindexf6f6ef436599..101eb944f13c100644arch/x86/include/asm/bootparam_utils.h +1
-1@@ -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.(quoted diff) +0
-0
b/arch/x86/include/asm/page_64_types.hindex793c14c372cb..288b065955b7100644arch/x86/include/asm/page_64_types.h +0
-1@@ -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 memorymap. */
#define
__PHYSICAL_MASK_SHIFT52(quoted diff) +0
-0
b/arch/x86/include/asm/pgtable_64_types.hindex88bca456da99..52e5f5f2240d100644arch/x86/include/asm/pgtable_64_types.h +1
-1@@ -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(quoted diff) +0
-0
b/arch/x86/kernel/cpu/microcode/amd.cindexe1f3ba19ba54..06d4e67f31ab100644arch/x86/kernel/cpu/microcode/amd.c +1
-1@@ -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" ;(quoted diff) +0
-0
b/arch/x86/kernel/kexec-bzimage64.cindex22f60dd26460..b07e7069b09e100644
arch/x86/kernel/kexec-bzimage64.c static void *bzImage64_load(struct kimage *image, char · line 419
Quoted 4 lines
arch/x86/kernel/kexec-bzimage64.c +0
-1@@ -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
*/
Quoted 35 lines
arch/x86/kernel/kexec-bzimage64.c +1
-0+/* 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? */ arch/x86/kernel/pci-dma.c +1
-1@@ -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)arch/x86/mm/tlb.c +1
-1@@ -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 (quoted diff) +0
-0
b/arch/x86/platform/pvh/enlighten.cindex1861a2ba0f2b..c0a502f7e3a7100644
arch/x86/platform/pvh/enlighten.c static void __init init_pvh_bootparams(bool xen_guest) · line 91
Quoted 7 lines
arch/x86/platform/pvh/enlighten.c +1
-1@@ -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
drivers/acpi/Kconfig config ACPI_CUSTOM_DSDT_FILE · line 335
Quoted 9 lines
arch/x86/platform/pvh/enlighten.c +0
-0* environment (i.e. hardware_subarch 0). drivers/acpi/Kconfig +0
-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.
drivers/acpi/Kconfig config ACPI_TABLE_UPGRADE · line 355
Quoted 7 lines
drivers/acpi/Kconfig +1
-1- 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
drivers/acpi/Kconfig config ACPI_TABLE_UPGRADE · line 356
Quoted 1 line
drivers/acpi/Kconfig +0
-0via initrd. No functional change if no ACPI tables are passed
via
drivers/acpi/Kconfig config ACPI_TABLE_UPGRADE
Quoted 3 lines
drivers/acpi/Kconfig +1
-1initrd, 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
drivers/acpi/Kconfig config ACPI_TABLE_OVERRIDE_VIA_BUILTIN_INITRD · line 365
Quoted 5 lines
drivers/acpi/Kconfig +0
-0config 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
drivers/acpi/Kconfig config ACPI_TABLE_OVERRIDE_VIA_BUILTIN_INITRD
Quoted 4 lines
drivers/acpi/Kconfig +1
-1from built-in uncompressed initrd. - See Documentation/acpi/initrd_table_override.txt for details + See Documentation/admin-guide/acpi/initrd_table_override.rst for
details
drivers/acpi/Kconfig config ACPI_DEBUG · line 376
Quoted 7 lines
drivers/acpi/Kconfig +0
-0config 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
drivers/acpi/Kconfig config ACPI_DEBUG · line 377
Quoted 2 lines
drivers/acpi/Kconfig +1
-1- parameters documented in Documentation/acpi/debug.txt and + parameters documented in Documentation/firmware-guide/acpi/
debug.rst and
drivers/acpi/Kconfig config ACPI_CUSTOM_METHOD · line 446
Quoted 6 lines
Documentation/admin-guide/kernel-parameters.rstto control the type and amount of debug output.drivers/acpi/Kconfig +0
-0@@ -445,7 +445,7 @@ config ACPI_CUSTOM_METHOD help This debug facility allows ACPI AML methods to be inserted and/
or
drivers/acpi/Kconfig config ACPI_CUSTOM_METHOD
Quoted 5 lines
drivers/acpi/Kconfig +1
-1replaced 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
drivers/acpi/Kconfig config ACPI_CUSTOM_METHOD · line 451
Quoted 1 line
drivers/acpi/Kconfig +0
-0kernel memory to be written to by root (uid=0) users, allowing
them
Quoted 75 lines
(quoted diff) +0
-0
b/drivers/net/ethernet/faraday/ftgmac100.cindexb17b79e612a3..ac6280ad43a1100644drivers/net/ethernet/faraday/ftgmac100.c +1
-1@@ -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);(quoted diff) +0
-0
b/drivers/staging/fieldbus/Documentation/fieldbus_dev.txtindex56af3f650fa3..89fb8e14676f100644drivers/staging/fieldbus/Documentation/fieldbus_dev.txt +0
-0@@ -54,8 +54,8 @@ a limited few common behaviours and properties. Thisallows us to define a simple interface consisting of a character device and a set of sysfs files:
See:
drivers/staging/fieldbus/Documentation/fieldbus_dev.txt +2
-2-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 gettheir diff --git
a/drivers/vhost/vhost.cb/drivers/vhost/vhost.cindex1e3ed41ae1f3..69938dbae2d0100644drivers/vhost/vhost.c +1
-1@@ -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) {include/acpi/acpi_drivers.h +1
-1@@ -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.
*/
#defineACPI_BUS_COMPONENT0x00010000include/linux/fs_context.h +0
-0@@ -85,7 +85,7 @@ struct fs_parameter {* Superblock creation fills in ->root whereas reconfiguration begins with this * already set.
*
- * SeeDocumentation/filesystems/mounting.txt
+ * SeeDocumentation/filesystems/mount_api.txt
*/
structfs_context{include/linux/fs_context.h +0
-0const struct fs_context_operations *ops;include/linux/lsm_hooks.h +0
-0
include/linux/lsm_hooks.h line 83
Quoted 8 lines
include/linux/lsm_hooks.h +1
-1@@ -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
mm/Kconfig config MEMORY_HOTPLUG_DEFAULT_ONLINE · line 165
Quoted 6 lines
mm/Kconfig +0
-0@@ -165,7 +165,7 @@ config MEMORY_HOTPLUG_DEFAULT_ONLINE onlining policy (/sys/devices/system/memory/auto_online_blocks)
which
mm/Kconfig config MEMORY_HOTPLUG_DEFAULT_ONLINE · line 166
Quoted 1 line
mm/Kconfig +0
-0determines what happens to newly added memory regions. Policy
setting
Quoted 6 lines
mm/Kconfig +1
-1can always be changed at runtime. - See Documentation/memory-hotplug.txt for more information. + See Documentation/admin-guide/mm/memory-hotplug.rst for moreinformation.
Say Y here if you want all hot-plugged memory blocks to appear
in
Quoted 60 lines
mm/Kconfig +0
-0'online' state by default.security/Kconfig +1
-1@@ -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"tools/include/linux/err.h +1
-1@@ -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(quoted diff) +0
-0
b/tools/objtool/Documentation/stack-validation.txtindex4dd11a554b9b..de094670050b100644tools/objtool/Documentation/stack-validation.txt +0
-0@@ -21,7 +21,7 @@ instructions). Similarly, it knows how to follow switchstatements, for which gcc sometimes uses jump tables.
(Objtool also has an 'orc generate' subcommand which generates debuginfo
tools/objtool/Documentation/stack-validation.txt +2
-2-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(quoted diff) +0
-0
b/tools/testing/selftests/x86/protection_keys.cindex5d546dcdbc80..798a5ddeee55100644tools/testing/selftests/x86/protection_keys.c +0
-1@@ -1,6 +1,6 @@// SPDX-License-Identifier: GPL-2.0 /* -* Tests x86 Memory Protection Keys (see
Quoted 4 lines
Documentation/x86/protection-keys.txt) + * Tests x86 Memory Protection Keys (seeDocumentation/x86/protection-keys.rst) *
* There are examples in here of:
* * how to set protection keys on memory
_______________________________________________
Virtualization mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
Federico Vaga
maintainerRe: [PATCH 10/10] docs: fix broken documentation links
In reply to Mauro Carvalho ChehabQuoted 73 lines · CEST Mauro Carvalho Chehab
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 <[email protected]>--- Documentation/acpi/dsd/leds.txt | 2 +- Documentation/admin-guide/kernel-parameters.rst | 6 +++--- Documentation/admin-guide/kernel-parameters.txt | 16 ++++++++-------- Documentation/admin-guide/ras.rst | 2 +- .../devicetree/bindings/net/fsl-enetc.txt | 7 +++---- .../bindings/pci/amlogic,meson-pcie.txt | 2 +- .../bindings/regulator/qcom,rpmh-regulator.txt | 2 +- Documentation/devicetree/booting-without-of.txt | 2 +- Documentation/driver-api/gpio/board.rst | 2 +- Documentation/driver-api/gpio/consumer.rst | 2 +- .../firmware-guide/acpi/enumeration.rst | 2 +- .../firmware-guide/acpi/method-tracing.rst | 2 +- Documentation/i2c/instantiating-devices | 2 +- Documentation/sysctl/kernel.txt | 4 ++-- .../translations/it_IT/process/4.Coding.rst | 2 +- .../translations/it_IT/process/howto.rst | 2 +- .../it_IT/process/stable-kernel-rules.rst | 4 ++-- .../translations/zh_CN/process/4.Coding.rst | 2 +- Documentation/x86/x86_64/5level-paging.rst | 2 +- Documentation/x86/x86_64/boot-options.rst | 4 ++-- .../x86/x86_64/fake-numa-for-cpusets.rst | 2 +- MAINTAINERS | 6 +++--- arch/arm/Kconfig | 2 +- arch/arm64/kernel/kexec_image.c | 2 +- arch/powerpc/Kconfig | 2 +- arch/x86/Kconfig | 16 ++++++++-------- arch/x86/Kconfig.debug | 2 +- arch/x86/boot/header.S | 2 +- arch/x86/entry/entry_64.S | 2 +- arch/x86/include/asm/bootparam_utils.h | 2 +- arch/x86/include/asm/page_64_types.h | 2 +- arch/x86/include/asm/pgtable_64_types.h | 2 +- arch/x86/kernel/cpu/microcode/amd.c | 2 +- arch/x86/kernel/kexec-bzimage64.c | 2 +- arch/x86/kernel/pci-dma.c | 2 +- arch/x86/mm/tlb.c | 2 +- arch/x86/platform/pvh/enlighten.c | 2 +- drivers/acpi/Kconfig | 10 +++++----- drivers/net/ethernet/faraday/ftgmac100.c | 2 +- .../fieldbus/Documentation/fieldbus_dev.txt | 4 ++-- drivers/vhost/vhost.c | 2 +- include/acpi/acpi_drivers.h | 2 +- include/linux/fs_context.h | 2 +- include/linux/lsm_hooks.h | 2 +- mm/Kconfig | 2 +- security/Kconfig | 2 +- tools/include/linux/err.h | 2 +- tools/objtool/Documentation/stack-validation.txt | 4 ++-- tools/testing/selftests/x86/protection_keys.c | 2 +- 49 files changed, 78 insertions(+), 79 deletions(-)(quoted diff) +0
-0
b/Documentation/acpi/dsd/leds.txtindex81a63af42ed2..cc58b1a574c5100644Documentation/acpi/dsd/leds.txt +0
-0@@ -96,4 +96,4 @@ where<URL:http://www.uefi.org/sites/default/files/resources/_DSD-hierarchical-da ta-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(quoted diff) +0
-0
b/Documentation/admin-guide/kernel-parameters.rstindex0124980dca2d..8d3273e32eb1100644
Documentation/admin-guide/kernel-parameters.rst parameter is applicable:: · line 170
Quoted 4 lines
Documentation/admin-guide/kernel-parameters.rst +0
-1@@ -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
.
Quoted 23 lines
Documentation/admin-guide/kernel-parameters.rst +1
-0+ 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 theoption:: 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 extremeDocumentation/admin-guide/kernel-parameters.rst +2
-2-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(quoted diff) +0
-0
b/Documentation/admin-guide/kernel-parameters.txtindex138f6664b2e2..bc5f202d42ec100644
Documentation/admin-guide/kernel-parameters.txt line 55
Quoted 3 lines
Documentation/admin-guide/kernel-parameters.txt +0
-0@@ -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/admin-guide/kernel-parameters.txt line 56
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +0
-1- Documentation/acpi/debug.txt for more
information about
Documentation/admin-guide/kernel-parameters.txt line 56
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +1
-0+ Documentation/firmware-guide/acpi/debug.rst
for more information about
Documentation/admin-guide/kernel-parameters.txt line 965
Quoted 7 lines
Documentation/admin-guide/kernel-parameters.txt +0
-0debug layers and levels. Enable processor driver info messages:@@ -963,7 +963,7 @@ for details. nompx [X86] Disables Intel Memory Protection
Extensions.
Documentation/admin-guide/kernel-parameters.txt line 966
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +0
-1- See Documentation/x86/intel_mpx.txt for
more
Documentation/admin-guide/kernel-parameters.txt line 966
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +1
-0+ See Documentation/x86/intel_mpx.rst for
more
Documentation/admin-guide/kernel-parameters.txt
Quoted 3 lines
Documentation/admin-guide/kernel-parameters.txt +0
-0information about the feature. nopku [X86] Disable Memory Protection Keys CPU
feature found
Documentation/admin-guide/kernel-parameters.txt line 1189
Quoted 2 lines
Documentation/admin-guide/kernel-parameters.txt +0
-0@@ -1189,7 +1189,7 @@ that is to be dynamically loaded by Linux.
If there are
Documentation/admin-guide/kernel-parameters.txt line 1190
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +0
-0multiple variables with the same name but
with different
Documentation/admin-guide/kernel-parameters.txt line 1191
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +0
-0vendor GUIDs, all of them will be loaded.
See
Documentation/admin-guide/kernel-parameters.txt line 1192
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +0
-1- Documentation/acpi/ssdt-overlays.txt for
details.
Documentation/admin-guide/kernel-parameters.txt line 1192
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +1
-0+ Documentation/admin-guide/acpi/ssdt-
overlays.rst for details.
Documentation/admin-guide/kernel-parameters.txt line 2386
Quoted 8 lines
Documentation/admin-guide/kernel-parameters.txt +0
-1eisa_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
Documentation/admin-guide/kernel-parameters.txt line 2386
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +1
-0+ mce=option [X86-64] See Documentation/x86/x86_64/boot-
options.rst
Documentation/admin-guide/kernel-parameters.txt line 2440
Quoted 6 lines
Documentation/admin-guide/kernel-parameters.txt +0
-0md= [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
Documentation/admin-guide/kernel-parameters.txt
Quoted 3 lines
Documentation/admin-guide/kernel-parameters.txt +1
-1option. - See Documentation/memory-hotplug.txt. + See Documentation/admin-guide/mm/memory-
hotplug.rst.
Documentation/admin-guide/kernel-parameters.txt line 2528
Quoted 5 lines
Documentation/admin-guide/kernel-parameters.txt +0
-0memmap=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
Documentation/admin-guide/kernel-parameters.txt
Quoted 3 lines
Documentation/admin-guide/kernel-parameters.txt +0
-1mem_encrypt=off: Do not activate SME - Refer to Documentation/x86/amd-memory-
encryption.txt
Documentation/admin-guide/kernel-parameters.txt line 2531
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +1
-0+ Refer to Documentation/x86/amd-memory-
encryption.rst
Documentation/admin-guide/kernel-parameters.txt line 2532
Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +0
-0for details on when memory encryption can
be activated.
Documentation/admin-guide/kernel-parameters.txt line 5054
Quoted 13 lines
Documentation/admin-guide/kernel-parameters.txt +1
-1mem_sleep_default= [SUSPEND] Default system suspend mode:@@ -3528,7 +3528,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 }@@ -5054,7 +5054,7 @@ Can be used multiple times for multiple
devices.
Documentation/admin-guide/kernel-parameters.txt line 5055
Quoted 2 lines
Documentation/admin-guide/kernel-parameters.txt +0
-0vga= [BOOT,X86-32] Select a particular video
mode
Documentation/admin-guide/kernel-parameters.txt
Quoted 5 lines
Documentation/admin-guide/kernel-parameters.txt +1
-1- 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
Quoted 60 lines
(quoted diff) +0
-0
b/Documentation/admin-guide/ras.rstindexc7495e42e6f4..2b20f5f7380d100644Documentation/admin-guide/ras.rst +1
-1@@ -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 *************************************(quoted diff) +0
-0
b/Documentation/devicetree/bindings/net/fsl-enetc.txtindexc812e25ae90f..25fc687419db100644Documentation/devicetree/bindings/net/fsl-enetc.txt +3
-4@@ -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:(quoted diff) +0
-0
b/Documentation/devicetree/bindings/pci/amlogic,meson-pcie.txtindex12b18f82d441..efa2c8b9b85a100644Documentation/devicetree/bindings/pci/amlogic,meson-pcie.txt +0
-0@@ -3,7 +3,7 @@ Amlogic Meson AXG DWC PCIE SoC controller Amlogic Meson PCIe host controller is based on the Synopsys DesignWare PCIcore. It shares common functions with the PCIe DesignWare core driver and inherits common properties defined in
Documentation/devicetree/bindings/pci/amlogic,meson-pcie.txt +1
-1-Documentation/devicetree/bindings/pci/designware-pci.txt. +Documentation/devicetree/bindings/pci/designware-pcie.txt. Additional properties are described here:diff --git
a/Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txtb/Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txtindex7ef2dbe48e8a..14d2eee96b3d100644
Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txt Second Level Nodes - Regulators · line 97
Quoted 1 line
Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txt +0
-0@@ -97,7 +97,7 @@ Second Level Nodes - Regulators sent for this regulator including those which are
for a
Quoted 126 lines
Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txt +1
-1strictly lower power state. -Other properties defined in Documentation/devicetree/bindings/regulator.txt +Other properties defined in
Documentation/devicetree/bindings/regulator/regulator.txtmay 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 diff --gita/Documentation/devicetree/booting-without-of.txtb/Documentation/devicetree/booting-without-of.txtindexe86bd2f64117..60f8640f2b2f100644Documentation/devicetree/booting-without-of.txt +1
-1@@ -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(quoted diff) +0
-0
b/Documentation/driver-api/gpio/board.rstindexb37f3f7b8926..ce91518bf9f4100644Documentation/driver-api/gpio/board.rst +1
-1@@ -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 -------------(quoted diff) +0
-0
b/Documentation/driver-api/gpio/consumer.rstindex5e4d8aa68913..fdecb6d711db100644Documentation/driver-api/gpio/consumer.rst +0
-0@@ -437,7 +437,7 @@ case, it will be handled by the GPIO subsystemautomatically. However, if the
_DSDis not present, the mappings between GpioIo()/GpioInt() resources and GPIO connection IDs need to be provided by device drivers.Documentation/driver-api/gpio/consumer.rst +1
-1-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(quoted diff) +0
-0
b/Documentation/firmware-guide/acpi/enumeration.rstindex6b32b7be8c85..65f5bb5725ac100644Documentation/firmware-guide/acpi/enumeration.rst +1
-1@@ -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 moreinformation about the
_DSDbinding related to GPIOs.MFD devices
(quoted diff) +0
-0
b/Documentation/firmware-guide/acpi/method-tracing.rstindexd0b077b73f5f..0aa7e2c5d32a100644Documentation/firmware-guide/acpi/method-tracing.rst +0
-0@@ -68,7 +68,7 @@ c. Filter out the debug layer/level matched logs when thespecified
Where:
0xXXXXXXXX/0xYYYYYYYYDocumentation/firmware-guide/acpi/method-tracing.rst +1
-1- Refer to Documentation/acpi/debug.txt for possible debug layer/level + Refer to Documentation/firmware-guide/acpi/debug.rst for possibledebug layer/level masking values.
\PPPP.AAAA.TTTT.HHHH
Full path of a control method that can be found in the ACPI namespace.(quoted diff) +0
-0b/Documentation/i2c/instantiating-devices index
0d85ac1935b7..5a3e2f331e8c100644Documentation/i2c/instantiating-devices +0
-1@@ -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. +whichis currently located at
Documentation/firmware-guide/acpi/enumeration.rst.Method 2: Instantiate the devices explicitly
(quoted diff) +0
-0
b/Documentation/sysctl/kernel.txtindexf0c86fbb3b48..92f7f34b021a100644Documentation/sysctl/kernel.txt +0
-0@@ -155,7 +155,7 @@ is 0x15 and the full version number is 0x234, this filewill contain the value 340 =
0x154.See the
type_of_loaderandext_loader_typefields inDocumentation/sysctl/kernel.txt +1
-1-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 exampleabove, this file will contain the value 564 =
0x234.See the
type_of_loaderandext_loader_verfields inDocumentation/sysctl/kernel.txt +1
-1-Documentation/x86/boot.txt for additional information. +Documentation/x86/boot.rst for additional information. ==============================================================(quoted diff) +0
-0
b/Documentation/translations/it_IT/process/4.Coding.rstindexc05b89e616dd..1d23e951491f100644Documentation/translations/it_IT/process/4.Coding.rst +0
-0@@ -370,7 +370,7 @@ con cosa stanno lavorando. Consultate:
Documentation/ABI/READMEper avere una descrizione di come questi documenti devono essere impostati e quali informazioni devono essere fornite.
Quoted 6 lines
-Il file :ref:
Documentation/translations/it_IT/admin-guide/kernel-parameters.rst <kernelparameters>+Il file :ref:Documentation/admin-guide/kernel-parameters.rst <kernelparameters>descrive tutti i parametri di avvio del kernel. Ogni patch che aggiunga nuovi parametri dovrebbe aggiungere nuove voci a questo file.
ACK
I will provide later a patch that adds that translation (just the .rst file)
Quoted 10 lines
(quoted diff) +0
-0
b/Documentation/translations/it_IT/process/howto.rstindex9903ac7c566b..44e6077730e8100644Documentation/translations/it_IT/process/howto.rst +0
-0@@ -131,7 +131,7 @@ Di seguito una lista di file che sono presenti neisorgente del kernel e che "Linux kernel patch submission format"
Documentation/translations/it_IT/process/howto.rst +0
-1http://linux.yyz.us/patch-format.html - :ref:`Documentation/process/translations/it_IT/stable-api-nonsense.rst
Quoted 3 lines
<
it_stable_api_nonsense>+ :ref:Documentation/translations/it_IT/process/stable-api-nonsense.rst<it_stable_api_nonsense>`
ACK
Quoted 8 lines
Questo file descrive la motivazioni sottostanti la conscia decisione di
non avere un API stabile all'interno del kernel, incluso cose come: diff --gita/Documentation/translations/it_IT/process/stable-kernel-rules.rstb/Documentation/translations/it_IT/process/stable-kernel-rules.rstindex48e88e5ad2c5..4f206cee31a7100644Documentation/translations/it_IT/process/stable-kernel-rules.rst +0
-0@@ -33,7 +33,7 @@ Regole sul tipo di patch che vengono o non vengono
Quoted 8 lines
accettate nei sorgenti - Non deve includere alcuna correzione "banale" (correzioni grammaticali, pulizia dagli spazi bianchi, eccetera).
- Deve rispettare le regole scritte in
- :ref:`Documentation/translation/it_IT/process/submitting-patches.rst
<it_submittingpatches>+ :ref:Documentation/translations/it_IT/process/submitting-patches.rst<it_submittingpatches>` - Questa patch o una equivalente deve esistere già nei sorgenti principali di Linux
ACK
Quoted 11 lines
Documentation/translations/it_IT/process/stable-kernel-rules.rst +0
-0@@ -43,7 +43,7 @@ Procedura per sottomettere patch per i sorgenti -stable - Se la patch contiene modifiche a dei file nelle cartelle net/ o
drivers/net, allora seguite le linee guida descritte in
- :ref:`Documentation/translation/it_IT/networking/netdev-FAQ.rst
<it_netdev-FAQ>; + :ref:Documentation/translations/it_IT/networking/netdev-FAQ.rst<it_netdev-FAQ>`; ma solo dopo aver verificato al seguente indirizzo che la patch non sia già in coda:
ACK
Thanks for the fixes, out of curiosity. How did you spot those mistakes?
Quoted 106 lines
https://patchwork.ozlabs.org/bundle/davem/stable/?series=&submitter=&state=
*&q=&archive= diff --gita/Documentation/translations/zh_CN/process/4.Coding.rstb/Documentation/translations/zh_CN/process/4.Coding.rstindex5301e9d55255..8bb777941394100644Documentation/translations/zh_CN/process/4.Coding.rst +1
-1@@ -241,7 +241,7 @@ scripts/coccinelle目录下已经打包了相当多的内核“语义补丁” 任何添加新用户空间界面的代码(包括新的sysfs或/proc文件)都应该包含该界面的 文档,该文档使用户空间开发人员能够知道他们在使用什么。请参阅 -Documentation/abi/readme,了解如何格式化此文档以及需要提供哪些信息。 +Documentation/ABI/README,了解如何格式化此文档以及需要提供哪些信息。 文件 :ref:`Documentation/admin-guide/kernel-parameters.rst<kernelparameters>` 描述了内核的所有引导时间参数。任何添加新参数的补丁都应该向该文件添加适当的
(quoted diff) +0
-0
b/Documentation/x86/x86_64/5level-paging.rstindexab88a4514163..44856417e6a5100644Documentation/x86/x86_64/5level-paging.rst +0
-0@@ -20,7 +20,7 @@ physical address space. This "ought to be enough foranybody" ©. QEMU 2.9 and later support 5-level paging.
Virtual memory layout for 5-level paging is described in
Documentation/x86/x86_64/5level-paging.rst +1
-1-Documentation/x86/x86_64/mm.txt +Documentation/x86/x86_64/mm.rst Enabling 5-level paging(quoted diff) +0
-0
b/Documentation/x86/x86_64/boot-options.rstindex2f69836b8445..6a4285a3c7a4100644Documentation/x86/x86_64/boot-options.rst +0
-1@@ -9,7 +9,7 @@ only the AMD64 specific ones are listed here. Machine check ============= -Please see Documentation/x86/x86_64/machinecheck for sysfs runtimetunables. +Please see
Documentation/x86/x86_64/machinecheck.rstfor sysfs runtime tunables.mce=off
Documentation/x86/x86_64/boot-options.rst +1
-1Disable 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(quoted diff) +0
-0
b/Documentation/x86/x86_64/fake-numa-for-cpusets.rstindex74fbb78b3c67..04df57b9aa3f100644Documentation/x86/x86_64/fake-numa-for-cpusets.rst +0
-0@@ -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, seeDocumentation/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 diff --git a/MAINTAINERS b/MAINTAINERS
index0c84bf76d165..47aa4f6defb9100644MAINTAINERS +0
-0@@ -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.txtMAINTAINERS +3
-3-F: Documentation/hwmon/lochnagar +F: Documentation/hwmon/lochnagar.rst CISCO FCOE HBA DRIVER M: Satish Kharat <[email protected]>@@ -11272,7 +11272,7 @@ NXP FXAS21002C DRIVER M: Rui Miguel Silva <[email protected]> L: [email protected] 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@@ -13043,7 +13043,7 @@ M: Niklas Cassel <[email protected]> L: [email protected] S: Maintained F: drivers/net/ethernet/stmicro/stmmac/dwmac-qcom-ethqos.c -F: Documentation/devicetree/bindings/net/qcom,dwmac.txt +F: Documentation/devicetree/bindings/net/qcom,ethqos.txt QUALCOMM GENERIC INTERFACE I2C DRIVER M: Alok Chauhan <[email protected]>arch/arm/Kconfig +0
-0
arch/arm/Kconfig config SMP · line 1267
Quoted 6 lines
arch/arm/Kconfig +1
-1@@ -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
arch/arm64/kernel/kexec_image.c static void *image_load(struct kimage *image, · line 56
Quoted 12 lines
<http://tldp.org/HOWTO/SMP-HOWTO.html>.
(quoted diff) +0
-0
b/arch/arm64/kernel/kexec_image.cindex07bf740bea91..31cc2f423aa8100644arch/arm64/kernel/kexec_image.c +1
-1@@ -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
arch/powerpc/Kconfig config PPC_MEM_KEYS · line 898
Quoted 9 lines
arch/arm64/kernel/kexec_image.c +0
-0* is non-zero (practically speaking, since v3.17). */ h = (struct arm64_image_header *)kernel;arch/powerpc/Kconfig +0
-0@@ -898,7 +898,7 @@ config PPC_MEM_KEYS page-based protections, but without requiring modification of
the
arch/x86/Kconfig config SMP · line 395
Quoted 13 lines
arch/powerpc/Kconfig +1
-1page tables when an application changes protection domains. - For details, see Documentation/vm/protection-keys.rst + For details, see Documentation/x86/protection-keys.rst If unsure, say y.arch/x86/Kconfig +0
-0@@ -395,7 +395,7 @@ config SMP Y to "Enhanced Real Time Clock Support", below. The "Advanced
Power
arch/x86/Kconfig config SMP
Quoted 5 lines
arch/x86/Kconfig +1
-1Management" 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
Quoted 7 lines
<http://www.tldp.org/docs.html#howto>.
arch/x86/Kconfig +0
-0@@ -1290,7 +1290,7 @@ config MICROCODE the Linux kernel. The preferred method to load microcode from a detached initrd isdescribed - in
Documentation/x86/microcode.txt. For that you
need to
arch/x86/Kconfig config MICROCODE_OLD_INTERFACE · line 1330
Quoted 7 lines
enable + in
Documentation/x86/microcode.rst. For that you need to enableCONFIG_BLK_DEV_INITRDin order for the loader to be able to scan the initrd for microcode blobs.arch/x86/Kconfig +0
-0@@ -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
arch/x86/Kconfig config MICROCODE_OLD_INTERFACE · line 1331
Quoted 1 line
arch/x86/Kconfig +0
-0should've switched to the early loading method with the initrd
or
Quoted 24 lines
arch/x86/Kconfig +3
-3- 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 moreinformation. If you are unsure how to answer this question, answer N.
config
ARCH_PROC_KCORE_TEXT
arch/x86/Kconfig config MTRR · line 1783
Quoted 1 line
arch/x86/Kconfig +0
-0@@ -1783,7 +1783,7 @@ config MTRR You can safely say Y even if your machine doesn't have MTRRs,
you'll
Quoted 17 lines
arch/x86/Kconfig +2
-2just 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.
arch/x86/Kconfig config X86_INTEL_MEMORY_PROTECTION_KEYS · line 1911
Quoted 1 line
arch/x86/Kconfig +0
-0@@ -1911,7 +1911,7 @@ config X86_INTEL_MEMORY_PROTECTION_KEYS page-based protections, but without requiring modification of
the
arch/x86/boot/header.S start_sys_seg: .word SYSSEG
Quoted 25 lines
arch/x86/Kconfig +1
-1page tables when an application changes protection domains. - For details, see Documentation/x86/protection-keys.txt + For details, see Documentation/x86/protection-keys.rst If unsure, say y.arch/x86/Kconfig.debug +1
-1@@ -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_LEAKarch/x86/boot/header.S +0
-0@@ -313,7 +313,7 @@ start_sys_seg: .word SYSSEG
# obsolete and meaningless,
Quoted 3 lines
but just
type_of_loader: .byte 0 # 0 means ancient
bootloader, newer
Quoted 1 line
# bootloaders know
to change this.
arch/x86/boot/header.S
Quoted 1 line
arch/x86/boot/header.S +0
-1- # See
Documentation/x86/boot.txt for
arch/x86/boot/header.S
Quoted 1 line
arch/x86/boot/header.S +1
-0+ # See
Documentation/x86/boot.rst for
Quoted 78 lines
arch/x86/boot/header.S +0
-0# assigned ids # flags, unused bits must be zero (RFU) bit within loadflagsarch/x86/entry/entry_64.S +1
-1@@ -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(quoted diff) +0
-0
b/arch/x86/include/asm/bootparam_utils.hindexf6f6ef436599..101eb944f13c100644arch/x86/include/asm/bootparam_utils.h +1
-1@@ -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.(quoted diff) +0
-0
b/arch/x86/include/asm/page_64_types.hindex793c14c372cb..288b065955b7100644arch/x86/include/asm/page_64_types.h +0
-1@@ -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 memorymap. */
#define
__PHYSICAL_MASK_SHIFT52(quoted diff) +0
-0
b/arch/x86/include/asm/pgtable_64_types.hindex88bca456da99..52e5f5f2240d100644arch/x86/include/asm/pgtable_64_types.h +1
-1@@ -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(quoted diff) +0
-0
b/arch/x86/kernel/cpu/microcode/amd.cindexe1f3ba19ba54..06d4e67f31ab100644arch/x86/kernel/cpu/microcode/amd.c +1
-1@@ -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" ;(quoted diff) +0
-0
b/arch/x86/kernel/kexec-bzimage64.cindex22f60dd26460..b07e7069b09e100644
arch/x86/kernel/kexec-bzimage64.c static void *bzImage64_load(struct kimage *image, char · line 419
Quoted 4 lines
arch/x86/kernel/kexec-bzimage64.c +0
-1@@ -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
*/
Quoted 35 lines
arch/x86/kernel/kexec-bzimage64.c +1
-0+/* 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? */ arch/x86/kernel/pci-dma.c +1
-1@@ -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)arch/x86/mm/tlb.c +1
-1@@ -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 (quoted diff) +0
-0
b/arch/x86/platform/pvh/enlighten.cindex1861a2ba0f2b..c0a502f7e3a7100644
arch/x86/platform/pvh/enlighten.c static void __init init_pvh_bootparams(bool xen_guest) · line 91
Quoted 7 lines
arch/x86/platform/pvh/enlighten.c +1
-1@@ -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
drivers/acpi/Kconfig config ACPI_CUSTOM_DSDT_FILE · line 335
Quoted 9 lines
arch/x86/platform/pvh/enlighten.c +0
-0* environment (i.e. hardware_subarch 0). drivers/acpi/Kconfig +0
-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.
drivers/acpi/Kconfig config ACPI_TABLE_UPGRADE · line 355
Quoted 7 lines
drivers/acpi/Kconfig +1
-1- 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
drivers/acpi/Kconfig config ACPI_TABLE_UPGRADE · line 356
Quoted 1 line
drivers/acpi/Kconfig +0
-0via initrd. No functional change if no ACPI tables are passed
via
drivers/acpi/Kconfig config ACPI_TABLE_UPGRADE
Quoted 3 lines
drivers/acpi/Kconfig +1
-1initrd, 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
drivers/acpi/Kconfig config ACPI_TABLE_OVERRIDE_VIA_BUILTIN_INITRD · line 365
Quoted 5 lines
drivers/acpi/Kconfig +0
-0config 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
drivers/acpi/Kconfig config ACPI_TABLE_OVERRIDE_VIA_BUILTIN_INITRD
Quoted 4 lines
drivers/acpi/Kconfig +1
-1from built-in uncompressed initrd. - See Documentation/acpi/initrd_table_override.txt for details + See Documentation/admin-guide/acpi/initrd_table_override.rst for
details
drivers/acpi/Kconfig config ACPI_DEBUG · line 376
Quoted 7 lines
drivers/acpi/Kconfig +0
-0config 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
drivers/acpi/Kconfig config ACPI_DEBUG · line 377
Quoted 2 lines
drivers/acpi/Kconfig +1
-1- parameters documented in Documentation/acpi/debug.txt and + parameters documented in Documentation/firmware-guide/acpi/
debug.rst and
drivers/acpi/Kconfig config ACPI_CUSTOM_METHOD · line 446
Quoted 6 lines
Documentation/admin-guide/kernel-parameters.rstto control the type and amount of debug output.drivers/acpi/Kconfig +0
-0@@ -445,7 +445,7 @@ config ACPI_CUSTOM_METHOD help This debug facility allows ACPI AML methods to be inserted and/
or
drivers/acpi/Kconfig config ACPI_CUSTOM_METHOD
Quoted 5 lines
drivers/acpi/Kconfig +1
-1replaced 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
drivers/acpi/Kconfig config ACPI_CUSTOM_METHOD · line 451
Quoted 1 line
drivers/acpi/Kconfig +0
-0kernel memory to be written to by root (uid=0) users, allowing
them
Quoted 75 lines
(quoted diff) +0
-0
b/drivers/net/ethernet/faraday/ftgmac100.cindexb17b79e612a3..ac6280ad43a1100644drivers/net/ethernet/faraday/ftgmac100.c +1
-1@@ -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);(quoted diff) +0
-0
b/drivers/staging/fieldbus/Documentation/fieldbus_dev.txtindex56af3f650fa3..89fb8e14676f100644drivers/staging/fieldbus/Documentation/fieldbus_dev.txt +0
-0@@ -54,8 +54,8 @@ a limited few common behaviours and properties. Thisallows us to define a simple interface consisting of a character device and a set of sysfs files:
See:
drivers/staging/fieldbus/Documentation/fieldbus_dev.txt +2
-2-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 gettheir diff --git
a/drivers/vhost/vhost.cb/drivers/vhost/vhost.cindex1e3ed41ae1f3..69938dbae2d0100644drivers/vhost/vhost.c +1
-1@@ -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) {include/acpi/acpi_drivers.h +1
-1@@ -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.
*/
#defineACPI_BUS_COMPONENT0x00010000include/linux/fs_context.h +0
-0@@ -85,7 +85,7 @@ struct fs_parameter {* Superblock creation fills in ->root whereas reconfiguration begins with this * already set.
*
- * SeeDocumentation/filesystems/mounting.txt
+ * SeeDocumentation/filesystems/mount_api.txt
*/
structfs_context{include/linux/fs_context.h +0
-0const struct fs_context_operations *ops;include/linux/lsm_hooks.h +0
-0
include/linux/lsm_hooks.h line 83
Quoted 8 lines
include/linux/lsm_hooks.h +1
-1@@ -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
mm/Kconfig config MEMORY_HOTPLUG_DEFAULT_ONLINE · line 165
Quoted 6 lines
mm/Kconfig +0
-0@@ -165,7 +165,7 @@ config MEMORY_HOTPLUG_DEFAULT_ONLINE onlining policy (/sys/devices/system/memory/auto_online_blocks)
which
mm/Kconfig config MEMORY_HOTPLUG_DEFAULT_ONLINE · line 166
Quoted 1 line
mm/Kconfig +0
-0determines what happens to newly added memory regions. Policy
setting
Quoted 6 lines
mm/Kconfig +1
-1can always be changed at runtime. - See Documentation/memory-hotplug.txt for more information. + See Documentation/admin-guide/mm/memory-hotplug.rst for moreinformation.
Say Y here if you want all hot-plugged memory blocks to appear
in
Quoted 60 lines
mm/Kconfig +0
-0'online' state by default.security/Kconfig +1
-1@@ -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"tools/include/linux/err.h +1
-1@@ -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(quoted diff) +0
-0
b/tools/objtool/Documentation/stack-validation.txtindex4dd11a554b9b..de094670050b100644tools/objtool/Documentation/stack-validation.txt +0
-0@@ -21,7 +21,7 @@ instructions). Similarly, it knows how to follow switchstatements, for which gcc sometimes uses jump tables.
(Objtool also has an 'orc generate' subcommand which generates debuginfo
tools/objtool/Documentation/stack-validation.txt +2
-2-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(quoted diff) +0
-0
b/tools/testing/selftests/x86/protection_keys.cindex5d546dcdbc80..798a5ddeee55100644tools/testing/selftests/x86/protection_keys.c +0
-1@@ -1,6 +1,6 @@// SPDX-License-Identifier: GPL-2.0 /* -* Tests x86 Memory Protection Keys (see
Quoted 4 lines
Documentation/x86/protection-keys.txt) + * Tests x86 Memory Protection Keys (seeDocumentation/x86/protection-keys.rst) *
* There are examples in here of:
* * how to set protection keys on memory
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [PATCH 10/10] docs: fix broken documentation links
In reply to Mauro Carvalho ChehabQuoted 5 lines · Mauro Carvalho Chehab
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(a)kernel.org>
For the ACPI part:
Re: [PATCH 10/10] docs: fix broken documentation links
In reply to Mauro Carvalho ChehabQuoted 5 lines · Mauro Carvalho Chehab
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 <[email protected]>
For the ACPI part:
Re: [PATCH 10/10] docs: fix broken documentation links
In reply to Mauro Carvalho ChehabQuoted 5 lines · Mauro Carvalho Chehab
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 <[email protected]>
For the ACPI part:
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
PATCH 10/10 docs: fix broken documentation links
In reply to Mauro Carvalho ChehabMostly due to x86 and acpi conversion, several documentation links are still pointing to the old file. Fix them.
--- Documentation/acpi/dsd/leds.txt | 2 +- Documentation/admin-guide/kernel-parameters.rst | 6 +++--- Documentation/admin-guide/kernel-parameters.txt | 16 ++++++++-------- Documentation/admin-guide/ras.rst | 2 +- .../devicetree/bindings/net/fsl-enetc.txt | 7 +++---- .../bindings/pci/amlogic,meson-pcie.txt | 2 +- .../bindings/regulator/qcom,rpmh-regulator.txt | 2 +- Documentation/devicetree/booting-without-of.txt | 2 +- Documentation/driver-api/gpio/board.rst | 2 +- Documentation/driver-api/gpio/consumer.rst | 2 +- .../firmware-guide/acpi/enumeration.rst | 2 +- .../firmware-guide/acpi/method-tracing.rst | 2 +- Documentation/i2c/instantiating-devices | 2 +- Documentation/sysctl/kernel.txt | 4 ++-- .../translations/it_IT/process/4.Coding.rst | 2 +- .../translations/it_IT/process/howto.rst | 2 +- .../it_IT/process/stable-kernel-rules.rst | 4 ++-- .../translations/zh_CN/process/4.Coding.rst | 2 +- Documentation/x86/x86_64/5level-paging.rst | 2 +- Documentation/x86/x86_64/boot-options.rst | 4 ++-- .../x86/x86_64/fake-numa-for-cpusets.rst | 2 +- MAINTAINERS | 6 +++--- arch/arm/Kconfig | 2 +- arch/arm64/kernel/kexec_image.c | 2 +- arch/powerpc/Kconfig | 2 +- arch/x86/Kconfig | 16 ++++++++-------- arch/x86/Kconfig.debug | 2 +- arch/x86/boot/header.S | 2 +- arch/x86/entry/entry_64.S | 2 +- arch/x86/include/asm/bootparam_utils.h | 2 +- arch/x86/include/asm/page_64_types.h | 2 +- arch/x86/include/asm/pgtable_64_types.h | 2 +- arch/x86/kernel/cpu/microcode/amd.c | 2 +- arch/x86/kernel/kexec-bzimage64.c | 2 +- arch/x86/kernel/pci-dma.c | 2 +- arch/x86/mm/tlb.c | 2 +- arch/x86/platform/pvh/enlighten.c | 2 +- drivers/acpi/Kconfig | 10 +++++----- drivers/net/ethernet/faraday/ftgmac100.c | 2 +- .../fieldbus/Documentation/fieldbus_dev.txt | 4 ++-- drivers/vhost/vhost.c | 2 +- include/acpi/acpi_drivers.h | 2 +- include/linux/fs_context.h | 2 +- include/linux/lsm_hooks.h | 2 +- mm/Kconfig | 2 +- security/Kconfig | 2 +- tools/include/linux/err.h | 2 +- tools/objtool/Documentation/stack-validation.txt | 4 ++-- tools/testing/selftests/x86/protection_keys.c | 2 +- 49 files changed, 78 insertions(+), 79 deletions(-)
Documentation/acpi/dsd/leds.txt +1 -1
@@ -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
Documentation/admin-guide/kernel-parameters.rst +3 -3
@@ -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
Documentation/admin-guide/kernel-parameters.txt +8 -8
@@ -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/x86/amd-memory-encryption.rst for details on when memory encryption can be activated. mem_sleep_default= [SUSPEND] Default system suspend mode:
@@ -3528,7 +3528,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 }
@@ -5054,7 +5054,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
Documentation/admin-guide/ras.rst +1 -1
@@ -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 *************************************
Documentation/devicetree/bindings/net/fsl-enetc.txt +3 -4
@@ -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:
Documentation/devicetree/bindings/pci/amlogic,meson-pcie.txt +1 -1
@@ -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:
Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txt +1 -1
@@ -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
Documentation/devicetree/booting-without-of.txt +1 -1
@@ -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
Documentation/driver-api/gpio/board.rst +1 -1
@@ -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 -------------
Documentation/driver-api/gpio/consumer.rst +1 -1
@@ -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
Documentation/firmware-guide/acpi/enumeration.rst +1 -1
@@ -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
Documentation/firmware-guide/acpi/method-tracing.rst +1 -1
@@ -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.
Documentation/i2c/instantiating-devices +1 -1
@@ -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
Documentation/sysctl/kernel.txt +2 -2
@@ -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. ==============================================================
Documentation/translations/it_IT/process/4.Coding.rst +1 -1
@@ -370,7 +370,7 @@ con cosa stanno lavorando. Consultate: Documentation/ABI/README per avere una descrizione di come questi documenti devono essere impostati e quali informazioni devono essere fornite. -Il file :ref:`Documentation/translations/it_IT/admin-guide/kernel-parameters.rst <kernelparameters>` +Il file :ref:`Documentation/admin-guide/kernel-parameters.rst <kernelparameters>` descrive tutti i parametri di avvio del kernel. Ogni patch che aggiunga nuovi parametri dovrebbe aggiungere nuove voci a questo file.
Documentation/translations/it_IT/process/howto.rst +1 -1
@@ -131,7 +131,7 @@ Di seguito una lista di file che sono presenti nei sorgente del kernel e che "Linux kernel patch submission format" http://linux.yyz.us/patch-format.html - :ref:`Documentation/process/translations/it_IT/stable-api-nonsense.rst <it_stable_api_nonsense>` + :ref:`Documentation/translations/it_IT/process/stable-api-nonsense.rst <it_stable_api_nonsense>` Questo file descrive la motivazioni sottostanti la conscia decisione di non avere un API stabile all'interno del kernel, incluso cose come:
Documentation/translations/it_IT/process/stable-kernel-rules.rst +2 -2
@@ -33,7 +33,7 @@ Regole sul tipo di patch che vengono o non vengono accettate nei sorgenti - Non deve includere alcuna correzione "banale" (correzioni grammaticali, pulizia dagli spazi bianchi, eccetera). - Deve rispettare le regole scritte in - :ref:`Documentation/translation/it_IT/process/submitting-patches.rst <it_submittingpatches>` + :ref:`Documentation/translations/it_IT/process/submitting-patches.rst <it_submittingpatches>` - Questa patch o una equivalente deve esistere già nei sorgenti principali di Linux
@@ -43,7 +43,7 @@ Procedura per sottomettere patch per i sorgenti -stable - Se la patch contiene modifiche a dei file nelle cartelle net/ o drivers/net, allora seguite le linee guida descritte in - :ref:`Documentation/translation/it_IT/networking/netdev-FAQ.rst <it_netdev-FAQ>`; + :ref:`Documentation/translations/it_IT/networking/netdev-FAQ.rst <it_netdev-FAQ>`; ma solo dopo aver verificato al seguente indirizzo che la patch non sia già in coda: https://patchwork.ozlabs.org/bundle/davem/stable/?series=&submitter=&state=*&q=&archive=
Documentation/translations/zh_CN/process/4.Coding.rst +1 -1
@@ -241,7 +241,7 @@ scripts/coccinelle目录下已经打包了相当多的内核“语义补丁” 任何添加新用户空间界面的代码(包括新的sysfs或/proc文件)都应该包含该界面的 文档,该文档使用户空间开发人员能够知道他们在使用什么。请参阅 -Documentation/abi/readme,了解如何格式化此文档以及需要提供哪些信息。 +Documentation/ABI/README,了解如何格式化此文档以及需要提供哪些信息。 文件 :ref:`Documentation/admin-guide/kernel-parameters.rst <kernelparameters>` 描述了内核的所有引导时间参数。任何添加新参数的补丁都应该向该文件添加适当的
Documentation/x86/x86_64/5level-paging.rst +1 -1
@@ -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
Documentation/x86/x86_64/boot-options.rst +2 -2
@@ -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
Documentation/x86/x86_64/fake-numa-for-cpusets.rst +1 -1
@@ -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
MAINTAINERS +3 -3
@@ -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 <[email protected]>
@@ -11272,7 +11272,7 @@ NXP FXAS21002C DRIVER M: Rui Miguel Silva <[email protected]> L: [email protected] 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
@@ -13043,7 +13043,7 @@ M: Niklas Cassel <[email protected]> L: [email protected] S: Maintained F: drivers/net/ethernet/stmicro/stmmac/dwmac-qcom-ethqos.c -F: Documentation/devicetree/bindings/net/qcom,dwmac.txt +F: Documentation/devicetree/bindings/net/qcom,ethqos.txt QUALCOMM GENERIC INTERFACE I2C DRIVER M: Alok Chauhan <[email protected]>
arch/arm/Kconfig +1 -1
@@ -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>.
arch/arm64/kernel/kexec_image.c +1 -1
@@ -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;
arch/powerpc/Kconfig +1 -1
@@ -898,7 +898,7 @@ config PPC_MEM_KEYS page-based protections, but without requiring modification of the page tables when an application changes protection domains. - For details, see Documentation/vm/protection-keys.rst + For details, see Documentation/x86/protection-keys.rst If unsure, say y.
arch/x86/Kconfig +8 -8
@@ -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.
@@ -1911,7 +1911,7 @@ config X86_INTEL_MEMORY_PROTECTION_KEYS page-based protections, but without requiring modification of the page tables when an application changes protection domains. - For details, see Documentation/x86/protection-keys.txt + For details, see Documentation/x86/protection-keys.rst If unsure, say y.
arch/x86/Kconfig.debug +1 -1
@@ -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
arch/x86/boot/header.S +1 -1
@@ -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
arch/x86/entry/entry_64.S +1 -1
@@ -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
arch/x86/include/asm/bootparam_utils.h +1 -1
@@ -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.
arch/x86/include/asm/page_64_types.h +1 -1
@@ -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
arch/x86/include/asm/pgtable_64_types.h +1 -1
@@ -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
arch/x86/kernel/cpu/microcode/amd.c +1 -1
@@ -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" ;
arch/x86/kernel/kexec-bzimage64.c +1 -1
@@ -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? */
arch/x86/kernel/pci-dma.c +1 -1
@@ -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)
arch/x86/mm/tlb.c +1 -1
@@ -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
arch/x86/platform/pvh/enlighten.c +1 -1
@@ -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).
drivers/acpi/Kconfig +5 -5
@@ -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
drivers/net/ethernet/faraday/ftgmac100.c +1 -1
@@ -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);
drivers/staging/fieldbus/Documentation/fieldbus_dev.txt +2 -2
@@ -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
drivers/vhost/vhost.c +1 -1
@@ -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) {
include/acpi/acpi_drivers.h +1 -1
@@ -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
include/linux/fs_context.h +1 -1
@@ -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;
include/linux/lsm_hooks.h +1 -1
@@ -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
mm/Kconfig +1 -1
@@ -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.
security/Kconfig +1 -1
@@ -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"
tools/include/linux/err.h +1 -1
@@ -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
tools/objtool/Documentation/stack-validation.txt +2 -2
@@ -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
tools/testing/selftests/x86/protection_keys.c +1 -1
@@ -1,6 +1,6 @@// SPDX-License-Identifier: GPL-2.0 /* -* Tests x86 Memory Protection Keys (see Documentation/x86/protection-keys.txt) +* Tests x86 Memory Protection Keys (see Documentation/x86/protection-keys.rst) * * There are examples in here of: * * how to set protection keys on memory
Signature · 7 lines
2.21.0 _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
Federico Vaga
maintainerQuoted 10 lines · CEST Mauro Carvalho Chehab
There are several broken
Documentation/*references within the Kernel tree. There are some reasons for several of them:1. The acpi and x86 documentation files were renamed, but the references weren't updated;
2. The DT files have been converted to JSON format, causing them to be renamed;
3. Translated files point to future translation work still pending merge or require some action from someone that it is fluent at the translated language;
Hi Mauro
I am not sure to get what you mean in terms of actions but I think you are referring to the "empty" files I added in the Italian translations. I added those files to avoid broken links; the alternative would have been to not write those links or to point directly to the main document, but in both cases it easy to forget to update them later.
I chose to have links to "empty" files so that the document does not need to be updated later.
If you are not referring to those files than I am not understanding, can you point to a clear example?
Quoted 127 lines
4. Some files (specially at DT) weren't accepted yet, but there are already references for them (at
MAINTAINERSand on other DT files);
5. Some files got removed without addressing Documentation, with needs them to describe some things.This series addresses problems 1 and 2, plus other random trivial breakages. Problems 3 to 5 depend on either accepting a patch or some specific knowledge. So, won't be addressed by this series.
The first 4 patches improve the documentation script to address some corner cases I detected while doing this series. The remaining ones are documentation fixes, being the last one having just trivial renaming stuff all over the Kernel tree.
After this series, only those warnings will be reported on v5.2-rc1:
Removed file without a non-trivial documentation adjustment:
Documentation/cgroup-v1/blkio-controller.txt:Documentation/block/cfq-iosched.txtDocumentation/cgroup-v1/blkio-controller.txt:Documentation/block/cfq-iosched.txtThe documentation file uses cfq as an example, but it got removed recently. Some parts of doc should be re-written to use another scheduler as an example.
Files pending addition (as far as I identified, there were e-mails asking their inclusions, but it didn't happen upstream yet):
Documentation/devicetree/bindings/regulator/rohm,bd70528-regulator.txt:Documentation/devicetree/bindings/mfd/rohm,bd70528-pmic.txtDocumentation/driver-api/generic-counter.rst:Documentation/ABI/testing/sys-bus-counter-generic-sysfsDocumentation/driver-api/generic-counter.rst:Documentation/ABI/testing/sys-bus-counterMAINTAINERS:Documentation/devicetree/bindings/rng/samsung,exynos5250-trng.txtTranslation files with broken stuff:
Documentation/translations/it_IT/process/adding-syscalls.rst:Documentation/translations/it_IT/filesystems/sysfs.txtDocumentation/translations/it_IT/process/coding-style.rst:Documentation/translations/it_IT/kbuild/kconfig-language.txtDocumentation/translations/it_IT/process/magic-number.rst:Documentation/process/magic-numbers.rstDocumentation/translations/zh_CN/basic_profiling.txt:Documentation/basic_profilingDocumentation/translations/zh_CN/basic_profiling.txt:Documentation/basic_profilingDocumentation/translations/zh_CN/process/howto.rst:Documentation/DocBook/Mauro Carvalho Chehab (10):
scripts/documentation-file-ref-check: better handle translationsscripts/documentation-file-ref-check: exclude false-positivesscripts/documentation-file-ref-check: improve tools ref handlingscripts/documentation-file-ref-check: teach about .txt -> .yaml
renames
ABI: sysfs-devices-system-cpu: point to the right docs
isdn: mISDN: remove a bogus reference to a non-existing doc
mfd: madera: point to the right pinctrl binding file
dt: fix refs that were renamed to json with the same file name
dt: fix broken references to nand.txt
docs: fix broken documentation links.../ABI/testing/sysfs-devices-system-cpu | 3 +- Documentation/acpi/dsd/leds.txt | 2 +- .../admin-guide/kernel-parameters.rst | 6 +-- .../admin-guide/kernel-parameters.txt | 16 +++---- Documentation/admin-guide/ras.rst | 2 +- .../devicetree/bindings/arm/omap/crossbar.txt | 2 +- .../bindings/clock/samsung,s5pv210-clock.txt | 2 +- .../marvell,odmi-controller.txt | 2 +- .../bindings/leds/irled/spi-ir-led.txt | 2 +- .../bindings/mtd/amlogic,meson-nand.txt | 2 +- .../devicetree/bindings/mtd/gpmc-nand.txt | 2 +- .../devicetree/bindings/mtd/marvell-nand.txt | 2 +- .../devicetree/bindings/mtd/tango-nand.txt | 2 +- .../devicetree/bindings/net/fsl-enetc.txt | 7 ++- .../bindings/pci/amlogic,meson-pcie.txt | 2 +- .../regulator/qcom,rpmh-regulator.txt | 2 +- .../devicetree/booting-without-of.txt | 2 +- Documentation/driver-api/gpio/board.rst | 2 +- Documentation/driver-api/gpio/consumer.rst | 2 +- .../firmware-guide/acpi/enumeration.rst | 2 +- .../firmware-guide/acpi/method-tracing.rst | 2 +- Documentation/i2c/instantiating-devices | 2 +- Documentation/sysctl/kernel.txt | 4 +- .../translations/it_IT/process/4.Coding.rst | 2 +- .../translations/it_IT/process/howto.rst | 2 +- .../it_IT/process/stable-kernel-rules.rst | 4 +- .../translations/zh_CN/process/4.Coding.rst | 2 +- Documentation/x86/x86_64/5level-paging.rst | 2 +- Documentation/x86/x86_64/boot-options.rst | 4 +- .../x86/x86_64/fake-numa-for-cpusets.rst | 2 +- MAINTAINERS | 10 ++--- arch/arm/Kconfig | 2 +- arch/arm64/kernel/kexec_image.c | 2 +- arch/powerpc/Kconfig | 2 +- arch/x86/Kconfig | 16 +++---- arch/x86/Kconfig.debug | 2 +- arch/x86/boot/header.S | 2 +- arch/x86/entry/entry_64.S | 2 +- arch/x86/include/asm/bootparam_utils.h | 2 +- arch/x86/include/asm/page_64_types.h | 2 +- arch/x86/include/asm/pgtable_64_types.h | 2 +- arch/x86/kernel/cpu/microcode/amd.c | 2 +- arch/x86/kernel/kexec-bzimage64.c | 2 +- arch/x86/kernel/pci-dma.c | 2 +- arch/x86/mm/tlb.c | 2 +- arch/x86/platform/pvh/enlighten.c | 2 +- drivers/acpi/Kconfig | 10 ++--- drivers/isdn/mISDN/dsp_core.c | 2 - drivers/net/ethernet/faraday/ftgmac100.c | 2 +- .../fieldbus/Documentation/fieldbus_dev.txt | 4 +- drivers/vhost/vhost.c | 2 +- include/acpi/acpi_drivers.h | 2 +- include/linux/fs_context.h | 2 +- include/linux/lsm_hooks.h | 2 +- include/linux/mfd/madera/pdata.h | 3 +- mm/Kconfig | 2 +- scripts/documentation-file-ref-check | 44 +++++++++++++++---- security/Kconfig | 2 +- tools/include/linux/err.h | 2 +- .../Documentation/stack-validation.txt | 4 +- tools/testing/selftests/x86/protection_keys.c | 2 +- 61 files changed, 127 insertions(+), 102 deletions(-)
Hi Frederico,
Em Wed, 22 May 2019 00:54:48 +0200 Federico Vaga <[email protected]> escreveu:
Quoted 12 lines · CEST Mauro Carvalho Chehab
Quoted 10 lines
There are several broken
Documentation/*references within the Kernel tree. There are some reasons for several of them:1. The acpi and x86 documentation files were renamed, but the references weren't updated;
2. The DT files have been converted to JSON format, causing them to be renamed;
3. Translated files point to future translation work still pending merge or require some action from someone that it is fluent at the translated language;
Quoted 1 line
Hi Mauro
My main goal with this patchset is to get as close as possible to zero warnings, as this helps me on rebasing a documentation patch series I wrote with renames hundreds of file from .txt to .rst.
In the case of (3), the scripts/documentation-file-ref-check was unable to find some files pointed by Italian and Chinese translations. So, after this series, it will keep pointing for broken links there.
Quoted 10 lines
I am not sure to get what you mean in terms of actions but I think you are referring to the "empty" files I added in the Italian translations. I added those files to avoid broken links; the alternative would have been to not write those links or to point directly to the main document, but in both cases it easy to forget to update them later.
I chose to have links to "empty" files so that the document does not need to be updated later.If you are not referring to those files than I am not understanding, can you point to a clear example?
What I meant is that I can barely read Italian and have no glue on Chinese. So, I can't really address those properly :-) So, basically, it should be up to someone else fluent on such languages to address those.
Btw, I understand why you pointed to some non-existing files:
translating the Kernel's documents takes a lot of time[1].
[1] If I was doing a translation, I would probably have opted to keep pointing to the English doc and have a script to point me links to non-translated docs, but your way also works. The only drawback is that the script will keep pinpointing to translations with broken links, while the translation is not complete.
Thanks,
Mauro
Federico Vaga
maintainerQuoted 44 lines · CEST Mauro Carvalho Chehab
Hi Frederico,
Em Wed, 22 May 2019 00:54:48 +0200
Federico Vaga <[email protected]> escreveu:
Quoted 10 lines · CEST Mauro Carvalho Chehab
Quoted 9 lines
There are several broken
Documentation/*references within the Kernel tree. There are some reasons for several of them:1. The acpi and x86 documentation files were renamed, but the
references weren't updated;2. The DT files have been converted to JSON format, causing them
Quoted 8 lines
Quoted 6 lines
to be renamed;3. Translated files point to future translation work still pending merge
or require some action from someone that it is fluent at the translated language;
Hi Mauro
My main goal with this patchset is to get as close as possible to zero warnings, as this helps me on rebasing a documentation patch series I wrote with renames hundreds of file from .txt to .rst.
In the case of (3), the
scripts/documentation-file-ref-checkwas unable to find some files pointed by Italian and Chinese translations. So, after this series, it will keep pointing for broken links there.Quoted 11 lines
I am not sure to get what you mean in terms of actions but I think you are referring to the "empty" files I added in the Italian translations. I added
those files to avoid broken links; the alternative would have been to not write those links or to point directly to the main document, but in both cases it easy to forget to update them later.
I chose to have links to "empty" files so that the document does not need to be updated later.If you are not referring to those files than I am not understanding, can you point to a clear example?
Quoted 7 lines
What I meant is that I can barely read Italian and have no glue on Chinese. So, I can't really address those properly :-) So, basically, it should be up to someone else fluent on such languages to address those.
Btw, I understand why you pointed to some non-existing files:
translating the Kernel's documents takes a lot of time[1].
More than non-existing the file *should* be there, only that it says the translation is pending. So the tool should find the file without complaining.
I did not pay enough attention; I was not aware about the existence of that tool. Now that I filled my ignorance with a bit of knowledge I will use to fix those documents. Thank you
Quoted 9 lines
[1] If I was doing a translation, I would probably have opted to keep pointing to the English doc and have a script to point me links to non-translated docs, but your way also works. The only drawback is that the script will keep pinpointing to translations with broken links, while the translation is not complete.
Thanks,
Mauro