Skip to contentSkip to conversation

Some documentation fixes

PATCH Applied Mauro Carvalho Chehab 21 participants 59 messages May 29, 2019 – Jun 7, 2019

Subsystems (48)
lore
Share & tools
lore
#0 lore raw

cover Some documentation fixes

Fix several warnings and broken links.

This series was generated against linux-next, but was rebased to be applied at docs-next. It should apply cleanly on either tree.

There's a git tree with all of them applied on the top of docs/docs-next at:

https://git.linuxtv.org/mchehab/experimental.git/log/?h=fix_doc_links_v2

Mauro Carvalho Chehab (21):
ABI: sysfs-devices-system-cpu: point to the right docs
isdn: mISDN: remove a bogus reference to a non-existing doc
dt: fix broken references to nand.txt
docs: zh_CN: get rid of basic_profiling.txt
doc: it_IT: fix reference to magic-number.rst
docs: mm: numaperf.rst: get rid of a build warning
docs: bpf: get rid of two warnings
docs: mark orphan documents as such
docs: amd-memory-encryption.rst get rid of warnings
gpu: amdgpu: fix broken amdgpu_dma_buf.c references
gpu: i915.rst: Fix references to renamed files
docs: zh_CN: avoid duplicate citation references
docs: vm: hmm.rst: fix some warnings
docs: it: license-rules.rst: get rid of warnings
docs: gpio: driver.rst: fix a bad tag
docs: soundwire: locking: fix tags for a code-block
docs: security: trusted-encrypted.rst: fix code-block tag
docs: security: core.rst: Fix several warnings
docs: net: dpio-driver.rst: fix two codeblock warnings
docs: net: sja1105.rst: fix table format
docs: fix broken documentation links

Otto Sabart (1):
mfd: madera: Fix bad reference to pinctrl.txt file

 .../ABI/testing/sysfs-devices-system-cpu      |  3 +-
 Documentation/accelerators/ocxl.rst           |  2 +
 Documentation/acpi/dsd/leds.txt               |  2 +-
 .../admin-guide/kernel-parameters.rst         |  6 +-
 .../admin-guide/kernel-parameters.txt         | 16 ++---
 Documentation/admin-guide/mm/numaperf.rst     |  5 +-
 Documentation/admin-guide/ras.rst             |  2 +-
 Documentation/arm/stm32/overview.rst          |  2 +
 .../arm/stm32/stm32f429-overview.rst          |  2 +
 .../arm/stm32/stm32f746-overview.rst          |  2 +
 .../arm/stm32/stm32f769-overview.rst          |  2 +
 .../arm/stm32/stm32h743-overview.rst          |  2 +
 .../arm/stm32/stm32mp157-overview.rst         |  2 +
 Documentation/bpf/btf.rst                     |  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 +-
 Documentation/driver-api/gpio/driver.rst      |  2 +-
 .../driver-api/soundwire/locking.rst          |  4 +-
 .../firmware-guide/acpi/enumeration.rst       |  2 +-
 .../firmware-guide/acpi/method-tracing.rst    |  2 +-
 Documentation/gpu/amdgpu.rst                  |  4 +-
 Documentation/gpu/i915.rst                    |  6 +-
 Documentation/gpu/msm-crash-dump.rst          |  2 +
 Documentation/i2c/instantiating-devices       |  2 +-
 Documentation/interconnect/interconnect.rst   |  2 +
 Documentation/laptops/lg-laptop.rst           |  2 +
 .../freescale/dpaa2/dpio-driver.rst           |  4 +-
 Documentation/networking/dsa/sja1105.rst      |  6 +-
 Documentation/powerpc/isa-versions.rst        |  2 +
 Documentation/security/keys/core.rst          | 16 +++--
 .../security/keys/trusted-encrypted.rst       |  4 +-
 Documentation/sysctl/kernel.txt               |  4 +-
 .../translations/it_IT/process/howto.rst      |  2 +-
 .../it_IT/process/license-rules.rst           | 28 ++++----
 .../it_IT/process/magic-number.rst            |  2 +-
 .../it_IT/process/stable-kernel-rules.rst     |  4 +-
 .../translations/zh_CN/basic_profiling.txt    | 71 -------------------
 .../translations/zh_CN/process/4.Coding.rst   |  2 +-
 .../zh_CN/process/management-style.rst        |  4 +-
 .../zh_CN/process/programming-language.rst    | 28 ++++----
 .../virtual/kvm/amd-memory-encryption.rst     |  5 ++
 Documentation/virtual/kvm/vcpu-requests.rst   |  2 +
 Documentation/vm/hmm.rst                      |  9 ++-
 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/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 +-
 security/Kconfig                              |  2 +-
 tools/include/linux/err.h                     |  2 +-
 .../Documentation/stack-validation.txt        |  4 +-
 tools/testing/selftests/x86/protection_keys.c |  2 +-
 84 files changed, 183 insertions(+), 212 deletions(-)
 delete mode 100644 Documentation/translations/zh_CN/basic_profiling.txt
Signature · 7 lines
2.21.0


_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
#1 lore raw

PATCH 1/22 ABI: sysfs-devices-system-cpu: point to the right docs

The 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
index 1528239f69b2..87478ac6c2af 100644
@@ -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
Acked-by on v1 1/22
#2 lore raw

Re: [PATCH 01/22] ABI: sysfs-devices-system-cpu: point to the right docs

Quoted 6 lines · CEST Mauro Carvalho Chehab

The 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).

Quoted 19 lines
---
 Documentation/ABI/testing/sysfs-devices-system-cpu | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
Documentation/ABI/testing/sysfs-devices-system-cpu +2 -1
index 1528239f69b2..87478ac6c2af 100644
@@ -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
#3 lore raw

PATCH 2/22 isdn: mISDN: remove a bogus reference to a non-existing doc

In reply to Mauro Carvalho Chehab

The 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
index cd036e87335a..038e72a84b33 100644
@@ -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
#4 lore raw

PATCH 3/22 dt: fix broken references to nand.txt

In reply to Mauro Carvalho Chehab

The 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.

Fixes 212e49693592 ("dt-bindings: mtd: Add YAML schemas for the generic NAND options")
---
 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
index 3983c11e062c..5794ab1147c1 100644
@@ -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
index c059ab74ed88..44919d48d241 100644
@@ -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
index e0c790706b9b..7eeef1e1ed30 100644
@@ -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
index cd1bf2ac9055..91c8420241af 100644
@@ -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 · 6 lines
2.21.0


______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
#5 lore raw

PATCH 4/22 docs: zh_CN: get rid of basic_profiling.txt

In reply to Mauro Carvalho Chehab

Changeset 5700d1974818 ("docs: Get rid of the "basic profiling" guide") removed an old basic-profiling.txt file that was not updated over the last 11 years and won't reflect the post-perf era.

It makes no sense to keep its translation, so get rid of it too.

Fixes 5700d1974818 ("docs: Get rid of the "basic profiling" guide")
---
 .../translations/zh_CN/basic_profiling.txt    | 71 -------------------
 1 file changed, 71 deletions(-)
 delete mode 100644 Documentation/translations/zh_CN/basic_profiling.txt
Documentation/translations/zh_CN/basic_profiling.txt deleted +0 -71
deleted file mode 100644
index 1e6bf0bdf8f5..000000000000
@@ -1,71 +0,0 @@
-Chinese translated version of Documentation/basic_profiling
-
-If you have any comment or update to the content, please post to LKML directly.
-However, if you have problem communicating in English you can also ask the
-Chinese maintainer for help.  Contact the Chinese maintainer, if this
-translation is outdated or there is problem with translation.
-
-Chinese maintainer: Liang Xie <[email protected]>
----------------------------------------------------------------------
-Documentation/basic_profiling的中文翻译
-
-如果想评论或更新本文的内容,请直接发信到LKML。如果你使用英文交流有困难的话,也可
-以向中文版维护者求助。如果本翻译更新不及时或者翻译存在问题,请联系中文版维护者。
-
-中文版维护者: 谢良 Liang Xie <[email protected]>
-中文版翻译者: 谢良 Liang Xie <[email protected]>
-中文版校译者:
-以下为正文
----------------------------------------------------------------------
-
-下面这些说明指令都是非常基础的,如果你想进一步了解请阅读相关专业文档:)
-请不要再在本文档增加新的内容,但可以修复文档中的错误:)([email protected])
-感谢John Levon,Dave Hansen等在撰写时的帮助
-
-<test> 用于表示要测量的目标
-请先确保您已经有正确的System.map / vmlinux配置!
-
-对于linux系统来说,配置vmlinuz最容易的方法可能就是使用“make install”,然后修改
-/sbin/installkernel将vmlinux拷贝到/boot目录,而System.map通常是默认安装好的
-
-Readprofile
------------
-2.6系列内核需要版本相对较新的readprofile,比如util-linux 2.12a中包含的,可以从:
-
-http://www.kernel.org/pub/linux/utils/util-linux/ 下载
-
-大部分linux发行版已经包含了.
-
-启用readprofile需要在kernel启动命令行增加”profile=2“
-
-clear		readprofile -r
-		<test>
-dump output	readprofile -m /boot/System.map > captured_profile
-
-Oprofile
---------
-
-从http://oprofile.sourceforge.net/获取源代码(请参考Changes以获取匹配的版本)
-在kernel启动命令行增加“idle=poll”
-
-配置CONFIG_PROFILING=y和CONFIG_OPROFILE=y然后重启进入新kernel
-
-./configure --with-kernel-support
-make install
-
-想得到好的测量结果,请确保启用了本地APIC特性。如果opreport显示有0Hz CPU,
-说明APIC特性没有开启。另外注意idle=poll选项可能有损性能。
-
-One time setup:
-		opcontrol --setup --vmlinux=/boot/vmlinux
-
-clear		opcontrol --reset
-start		opcontrol --start
-		<test>
-stop		opcontrol --stop
-dump output	opreport >  output_file
-
-如果只看kernel相关的报告结果,请运行命令 opreport -l /boot/vmlinux > output_file
-
-通过reset选项可以清理过期统计数据,相当于重启的效果。
-
Signature · 1 line
2.21.0
Acked-by on v1 4/22
#6 lore raw

Re: [PATCH 04/22] docs: zh_CN: get rid of basic_profiling.txt

Quoted 9 lines · Mauro Carvalho Chehab

Changeset 5700d1974818 ("docs: Get rid of the "basic profiling" guide") removed an old basic-profiling.txt file that was not updated over the last 11 years and won't reflect the post-perf era.

It makes no sense to keep its translation, so get rid of it too.

Fixes 5700d1974818 ("docs: Get rid of the "basic profiling" guide")

---

#7 lore raw

PATCH 5/22 mfd: madera: Fix bad reference to pinctrl.txt file

In reply to Mauro Carvalho Chehab

From: Otto Sabart <[email protected]>

The pinctrl.txt file was converted into reStructuredText and moved into driver-api folder. This patch updates the broken reference.

Fixes 5a9b73832e9e ("pinctrl.txt: move it to the driver-api book")
---
 include/linux/mfd/madera/pdata.h | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
include/linux/mfd/madera/pdata.h +2 -1
index 8dc852402dbb..dd00ab824e5b 100644
@@ -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/driver-api/pinctl.rst)
  * @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
#8 lore raw

PATCH 6/22 doc: it_IT: fix reference to magic-number.rst

In reply to Mauro Carvalho Chehab

There's a typo at the referred file.

---
 Documentation/translations/it_IT/process/magic-number.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/translations/it_IT/process/magic-number.rst +1 -1
index 5281d53e57ee..ed1121d0ba84 100644
@@ -1,6 +1,6 @@
 .. include:: ../disclaimer-ita.rst
 
-:Original: :ref:`Documentation/process/magic-numbers.rst <magicnumbers>`
+:Original: :ref:`Documentation/process/magic-number.rst <magicnumbers>`
 :Translator: Federico Vaga <[email protected]>
 
 .. _it_magicnumbers:
Signature · 1 line
2.21.0
maintainer
#9 lore raw

Re: [PATCH 06/22] doc: it_IT: fix reference to magic-number.rst

Quoted 1 line · CEST Mauro Carvalho Chehab

There's a typo at the referred file.

I am about to send a patch that fixes all issues found by documentation-file-ref-check in Documentation/translations/it_IT.

Of course I fixed this as well.

Quoted 20 lines
---
 Documentation/translations/it_IT/process/magic-number.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
(quoted diff) +0 -0

b/Documentation/translations/it_IT/process/magic-number.rst index 5281d53e57ee..ed1121d0ba84 100644

Documentation/translations/it_IT/process/magic-number.rst +1 -1
@@ -1,6 +1,6 @@
 .. include:: ../disclaimer-ita.rst
 
-:Original: :ref:`Documentation/process/magic-numbers.rst <magicnumbers>`
+:Original: :ref:`Documentation/process/magic-number.rst <magicnumbers>`
 
 :Translator: Federico Vaga <[email protected]>
 

.. _it_magicnumbers:

#10 lore raw

PATCH 7/22 docs: mm: numaperf.rst: get rid of a build warning

In reply to Mauro Carvalho Chehab

When building it, it gets this warning:

Documentation/admin-guide/mm/numaperf.rst:168: WARNING: Footnote [1] is not referenced.

The problem is that this is not really a reference, as it is not mentioned within the documentation.

---
 Documentation/admin-guide/mm/numaperf.rst | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)
Documentation/admin-guide/mm/numaperf.rst +3 -2
index c067ed145158..a80c3c37226e 100644
@@ -165,5 +165,6 @@ write-through caching.
 ========
 See Also
 ========
-.. [1] https://www.uefi.org/sites/default/files/resources/ACPI_6_2.pdf
-       Section 5.2.27
+
+[1] https://www.uefi.org/sites/default/files/resources/ACPI_6_2.pdf
+- Section 5.2.27
Signature · 1 line
2.21.0
#11 lore raw

PATCH 8/22 docs: bpf: get rid of two warnings

In reply to Mauro Carvalho Chehab

Documentation/bpf/btf.rst:154: WARNING: Unexpected indentation. Documentation/bpf/btf.rst:163: WARNING: Unexpected indentation.

---
 Documentation/bpf/btf.rst | 2 ++
 1 file changed, 2 insertions(+)
Documentation/bpf/btf.rst +2 -0
index 8820360d00da..4ae022d274ab 100644
@@ -151,6 +151,7 @@ for the type. The maximum value of ``BTF_INT_BITS()`` is 128.
 
 The ``BTF_INT_OFFSET()`` specifies the starting bit offset to calculate values
 for this int. For example, a bitfield struct member has:
+
  * btf member bit offset 100 from the start of the structure,
  * btf member pointing to an int type,
  * the int type has ``BTF_INT_OFFSET() = 2`` and ``BTF_INT_BITS() = 4``
@@ -160,6 +161,7 @@ from bits ``100 + 2 = 102``.
 
 Alternatively, the bitfield struct member can be the following to access the
 same bits as the above:
+
  * btf member bit offset 102,
  * btf member pointing to an int type,
  * the int type has ``BTF_INT_OFFSET() = 0`` and ``BTF_INT_BITS() = 4``
Signature · 1 line
2.21.0
Acked-by on v1 8/22
#12 lore raw

Re: [PATCH 08/22] docs: bpf: get rid of two warnings

Quoted 5 lines · Mauro Carvalho Chehab

Documentation/bpf/btf.rst:154: WARNING: Unexpected indentation. Documentation/bpf/btf.rst:163: WARNING: Unexpected indentation.

Quoted 27 lines
---
 Documentation/bpf/btf.rst | 2 ++
 1 file changed, 2 insertions(+)
Documentation/bpf/btf.rst +2 -1
index 8820360d00da..4ae022d274ab 100644
@@ -151,6 +151,7 @@ for the type. The maximum value of ``BTF_INT_BITS()`` is 128.
 
 The ``BTF_INT_OFFSET()`` specifies the starting bit offset to calculate values
 for this int. For example, a bitfield struct member has:
+
  * btf member bit offset 100 from the start of the structure,
  * btf member pointing to an int type,
  * the int type has ``BTF_INT_OFFSET() = 2`` and ``BTF_INT_BITS() = 4``
@@ -160,6 +161,7 @@ from bits ``100 + 2 = 102``.
 
 Alternatively, the bitfield struct member can be the following to access the
 same bits as the above:
+
  * btf member bit offset 102,
  * btf member pointing to an int type,
  * the int type has ``BTF_INT_OFFSET() = 0`` and ``BTF_INT_BITS() = 4``
--

2.21.0

#13 lore raw

PATCH 9/22 docs: mark orphan documents as such

In reply to Mauro Carvalho Chehab

Sphinx doesn't like orphan documents:

Documentation/accelerators/ocxl.rst: WARNING: document isn't included in any toctree Documentation/arm/stm32/overview.rst: WARNING: document isn't included in any toctree Documentation/arm/stm32/stm32f429-overview.rst: WARNING: document isn't included in any toctree Documentation/arm/stm32/stm32f746-overview.rst: WARNING: document isn't included in any toctree Documentation/arm/stm32/stm32f769-overview.rst: WARNING: document isn't included in any toctree Documentation/arm/stm32/stm32h743-overview.rst: WARNING: document isn't included in any toctree Documentation/arm/stm32/stm32mp157-overview.rst: WARNING: document isn't included in any toctree Documentation/gpu/msm-crash-dump.rst: WARNING: document isn't included in any toctree Documentation/interconnect/interconnect.rst: WARNING: document isn't included in any toctree Documentation/laptops/lg-laptop.rst: WARNING: document isn't included in any toctree Documentation/powerpc/isa-versions.rst: WARNING: document isn't included in any toctree Documentation/virtual/kvm/amd-memory-encryption.rst: WARNING: document isn't included in any toctree Documentation/virtual/kvm/vcpu-requests.rst: WARNING: document isn't included in any toctree

So, while they aren't on any toctree, add :orphan: to them, in order to silent this warning.

---
 Documentation/accelerators/ocxl.rst                 | 2 ++
 Documentation/arm/stm32/overview.rst                | 2 ++
 Documentation/arm/stm32/stm32f429-overview.rst      | 2 ++
 Documentation/arm/stm32/stm32f746-overview.rst      | 2 ++
 Documentation/arm/stm32/stm32f769-overview.rst      | 2 ++
 Documentation/arm/stm32/stm32h743-overview.rst      | 2 ++
 Documentation/arm/stm32/stm32mp157-overview.rst     | 2 ++
 Documentation/gpu/msm-crash-dump.rst                | 2 ++
 Documentation/interconnect/interconnect.rst         | 2 ++
 Documentation/laptops/lg-laptop.rst                 | 2 ++
 Documentation/powerpc/isa-versions.rst              | 2 ++
 Documentation/virtual/kvm/amd-memory-encryption.rst | 2 ++
 Documentation/virtual/kvm/vcpu-requests.rst         | 2 ++
 13 files changed, 26 insertions(+)
Documentation/accelerators/ocxl.rst +2 -0
index 14cefc020e2d..b1cea19a90f5 100644
@@ -1,3 +1,5 @@
+:orphan:
+
 ========================================================
 OpenCAPI (Open Coherent Accelerator Processor Interface)
 ========================================================
Documentation/arm/stm32/overview.rst +2 -0
index 85cfc8410798..f7e734153860 100644
@@ -1,3 +1,5 @@
+:orphan:
+
 ========================
 STM32 ARM Linux Overview
 ========================
Documentation/arm/stm32/stm32f429-overview.rst +2 -0
index 18feda97f483..65bbb1c3b423 100644
@@ -1,3 +1,5 @@
+:orphan:
+
 STM32F429 Overview
 ==================
 
Documentation/arm/stm32/stm32f746-overview.rst +2 -0
index b5f4b6ce7656..42d593085015 100644
@@ -1,3 +1,5 @@
+:orphan:
+
 STM32F746 Overview
 ==================
 
Documentation/arm/stm32/stm32f769-overview.rst +2 -0
index 228656ced2fe..f6adac862b17 100644
@@ -1,3 +1,5 @@
+:orphan:
+
 STM32F769 Overview
 ==================
 
Documentation/arm/stm32/stm32h743-overview.rst +2 -0
index 3458dc00095d..c525835e7473 100644
@@ -1,3 +1,5 @@
+:orphan:
+
 STM32H743 Overview
 ==================
 
Documentation/arm/stm32/stm32mp157-overview.rst +2 -0
index 62e176d47ca7..2c52cd020601 100644
@@ -1,3 +1,5 @@
+:orphan:
+
 STM32MP157 Overview
 ===================
 
Documentation/gpu/msm-crash-dump.rst +2 -0
index 757cd257e0d8..240ef200f76c 100644
@@ -1,3 +1,5 @@
+:orphan:
+
 =====================
 MSM Crash Dump Format
 =====================
Documentation/interconnect/interconnect.rst +2 -0
index c3e004893796..56e331dab70e 100644
@@ -1,5 +1,7 @@
 .. SPDX-License-Identifier: GPL-2.0
 
+:orphan:
+
 =====================================
 GENERIC SYSTEM INTERCONNECT SUBSYSTEM
 =====================================
Documentation/laptops/lg-laptop.rst +2 -0
index aa503ee9b3bc..f2c2ffe31101 100644
@@ -1,5 +1,7 @@
 .. SPDX-License-Identifier: GPL-2.0+
 
+:orphan:
+
 LG Gram laptop extra features
 =============================
 
Documentation/powerpc/isa-versions.rst +2 -0
index 812e20cc898c..66c24140ebf1 100644
@@ -1,3 +1,5 @@
+:orphan:
+
 CPU to ISA Version Mapping
 ==========================
 
Documentation/virtual/kvm/amd-memory-encryption.rst +2 -0
index 659bbc093b52..33d697ab8a58 100644
@@ -1,3 +1,5 @@
+:orphan:
+
 ======================================
 Secure Encrypted Virtualization (SEV)
 ======================================
Documentation/virtual/kvm/vcpu-requests.rst +2 -0
index 5feb3706a7ae..c1807a1b92e6 100644
@@ -1,3 +1,5 @@
+:orphan:
+
 =================
 KVM VCPU Requests
 =================
Signature · 6 lines
2.21.0

_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
maintainer
#14 lore raw

Re: [PATCH 09/22] docs: mark orphan documents as such

Quoted 16 lines · Mauro Carvalho Chehab

Sphinx doesn't like orphan documents:

Documentation/accelerators/ocxl.rst: WARNING: document isn't included in any toctree Documentation/arm/stm32/overview.rst: WARNING: document isn't included in any toctree Documentation/arm/stm32/stm32f429-overview.rst: WARNING: document isn't included in any toctree Documentation/arm/stm32/stm32f746-overview.rst: WARNING: document isn't included in any toctree Documentation/arm/stm32/stm32f769-overview.rst: WARNING: document isn't included in any toctree Documentation/arm/stm32/stm32h743-overview.rst: WARNING: document isn't included in any toctree Documentation/arm/stm32/stm32mp157-overview.rst: WARNING: document isn't included in any toctree Documentation/gpu/msm-crash-dump.rst: WARNING: document isn't included in any toctree Documentation/interconnect/interconnect.rst: WARNING: document isn't included in any toctree Documentation/laptops/lg-laptop.rst: WARNING: document isn't included in any toctree Documentation/powerpc/isa-versions.rst: WARNING: document isn't included in any toctree Documentation/virtual/kvm/amd-memory-encryption.rst: WARNING: document isn't included in any toctree Documentation/virtual/kvm/vcpu-requests.rst: WARNING: document isn't included in any toctree

Quoted 4 lines

So, while they aren't on any toctree, add :orphan: to them, in order to silent this warning.

Please leave out KVM, I'll fix that instead. Thanks for the report!

Paolo

Quoted 146 lines
---
 Documentation/accelerators/ocxl.rst                 | 2 ++
 Documentation/arm/stm32/overview.rst                | 2 ++
 Documentation/arm/stm32/stm32f429-overview.rst      | 2 ++
 Documentation/arm/stm32/stm32f746-overview.rst      | 2 ++
 Documentation/arm/stm32/stm32f769-overview.rst      | 2 ++
 Documentation/arm/stm32/stm32h743-overview.rst      | 2 ++
 Documentation/arm/stm32/stm32mp157-overview.rst     | 2 ++
 Documentation/gpu/msm-crash-dump.rst                | 2 ++
 Documentation/interconnect/interconnect.rst         | 2 ++
 Documentation/laptops/lg-laptop.rst                 | 2 ++
 Documentation/powerpc/isa-versions.rst              | 2 ++
 Documentation/virtual/kvm/amd-memory-encryption.rst | 2 ++
 Documentation/virtual/kvm/vcpu-requests.rst         | 2 ++
 13 files changed, 26 insertions(+)
Documentation/accelerators/ocxl.rst +2 -0
index 14cefc020e2d..b1cea19a90f5 100644
@@ -1,3 +1,5 @@
+:orphan:
+
 ========================================================
 OpenCAPI (Open Coherent Accelerator Processor Interface)
 ========================================================
Documentation/arm/stm32/overview.rst +2 -0
index 85cfc8410798..f7e734153860 100644
@@ -1,3 +1,5 @@
+:orphan:
+
 ========================
 STM32 ARM Linux Overview
 ========================
Documentation/arm/stm32/stm32f429-overview.rst +2 -0
index 18feda97f483..65bbb1c3b423 100644
@@ -1,3 +1,5 @@
+:orphan:
+
 STM32F429 Overview
 ==================
 
Documentation/arm/stm32/stm32f746-overview.rst +2 -0
index b5f4b6ce7656..42d593085015 100644
@@ -1,3 +1,5 @@
+:orphan:
+
 STM32F746 Overview
 ==================
 
Documentation/arm/stm32/stm32f769-overview.rst +2 -0
index 228656ced2fe..f6adac862b17 100644
@@ -1,3 +1,5 @@
+:orphan:
+
 STM32F769 Overview
 ==================
 
Documentation/arm/stm32/stm32h743-overview.rst +2 -0
index 3458dc00095d..c525835e7473 100644
@@ -1,3 +1,5 @@
+:orphan:
+
 STM32H743 Overview
 ==================
 
Documentation/arm/stm32/stm32mp157-overview.rst +2 -0
index 62e176d47ca7..2c52cd020601 100644
@@ -1,3 +1,5 @@
+:orphan:
+
 STM32MP157 Overview
 ===================
 
Documentation/gpu/msm-crash-dump.rst +2 -0
index 757cd257e0d8..240ef200f76c 100644
@@ -1,3 +1,5 @@
+:orphan:
+
 =====================
 MSM Crash Dump Format
 =====================
Documentation/interconnect/interconnect.rst +2 -0
index c3e004893796..56e331dab70e 100644
@@ -1,5 +1,7 @@
 .. SPDX-License-Identifier: GPL-2.0
 
+:orphan:
+
 =====================================
 GENERIC SYSTEM INTERCONNECT SUBSYSTEM
 =====================================
Documentation/laptops/lg-laptop.rst +2 -0
index aa503ee9b3bc..f2c2ffe31101 100644
@@ -1,5 +1,7 @@
 .. SPDX-License-Identifier: GPL-2.0+
 
+:orphan:
+
 LG Gram laptop extra features
 =============================
 
Documentation/powerpc/isa-versions.rst +2 -0
index 812e20cc898c..66c24140ebf1 100644
@@ -1,3 +1,5 @@
+:orphan:
+
 CPU to ISA Version Mapping
 ==========================
 
Documentation/virtual/kvm/amd-memory-encryption.rst +2 -0
index 659bbc093b52..33d697ab8a58 100644
@@ -1,3 +1,5 @@
+:orphan:
+
 ======================================
 Secure Encrypted Virtualization (SEV)
 ======================================
Documentation/virtual/kvm/vcpu-requests.rst +0 -0
index 5feb3706a7ae..c1807a1b92e6 100644

Documentation/virtual/kvm/vcpu-requests.rst line 5

Quoted 5 lines
Documentation/virtual/kvm/vcpu-requests.rst +2 -0
@@ -1,3 +1,5 @@
+:orphan:
+
 =================
 KVM VCPU Requests
 =================

_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel

#15 lore raw

Re: [PATCH 09/22] docs: mark orphan documents as such

In reply to Mauro Carvalho Chehab

Le 30/05/2019 à 01:23, Mauro Carvalho Chehab a écrit :

Quoted 16 lines

Sphinx doesn't like orphan documents:

Documentation/accelerators/ocxl.rst: WARNING: document isn't included in any toctree Documentation/arm/stm32/overview.rst: WARNING: document isn't included in any toctree Documentation/arm/stm32/stm32f429-overview.rst: WARNING: document isn't included in any toctree Documentation/arm/stm32/stm32f746-overview.rst: WARNING: document isn't included in any toctree Documentation/arm/stm32/stm32f769-overview.rst: WARNING: document isn't included in any toctree Documentation/arm/stm32/stm32h743-overview.rst: WARNING: document isn't included in any toctree Documentation/arm/stm32/stm32mp157-overview.rst: WARNING: document isn't included in any toctree Documentation/gpu/msm-crash-dump.rst: WARNING: document isn't included in any toctree Documentation/interconnect/interconnect.rst: WARNING: document isn't included in any toctree Documentation/laptops/lg-laptop.rst: WARNING: document isn't included in any toctree Documentation/powerpc/isa-versions.rst: WARNING: document isn't included in any toctree Documentation/virtual/kvm/amd-memory-encryption.rst: WARNING: document isn't included in any toctree Documentation/virtual/kvm/vcpu-requests.rst: WARNING: document isn't included in any toctree

Quoted 2 lines

So, while they aren't on any toctree, add :orphan: to them, in order to silent this warning.

Are those files really not meant to be included in a toctree ?

Shouldn't we include them in the relevant toctree instead of just shutting up Sphinx warnings ?

Christophe

Quoted 153 lines
---
  Documentation/accelerators/ocxl.rst                 | 2 ++
  Documentation/arm/stm32/overview.rst                | 2 ++
  Documentation/arm/stm32/stm32f429-overview.rst      | 2 ++
  Documentation/arm/stm32/stm32f746-overview.rst      | 2 ++
  Documentation/arm/stm32/stm32f769-overview.rst      | 2 ++
  Documentation/arm/stm32/stm32h743-overview.rst      | 2 ++
  Documentation/arm/stm32/stm32mp157-overview.rst     | 2 ++
  Documentation/gpu/msm-crash-dump.rst                | 2 ++
  Documentation/interconnect/interconnect.rst         | 2 ++
  Documentation/laptops/lg-laptop.rst                 | 2 ++
  Documentation/powerpc/isa-versions.rst              | 2 ++
  Documentation/virtual/kvm/amd-memory-encryption.rst | 2 ++
  Documentation/virtual/kvm/vcpu-requests.rst         | 2 ++
  13 files changed, 26 insertions(+)
Documentation/accelerators/ocxl.rst +2 -0
index 14cefc020e2d..b1cea19a90f5 100644
@@ -1,3 +1,5 @@
+:orphan:
+
  ========================================================
  OpenCAPI (Open Coherent Accelerator Processor Interface)
  ========================================================
Documentation/arm/stm32/overview.rst +2 -0
index 85cfc8410798..f7e734153860 100644
@@ -1,3 +1,5 @@
+:orphan:
+
  ========================
  STM32 ARM Linux Overview
  ========================
Documentation/arm/stm32/stm32f429-overview.rst +2 -0
index 18feda97f483..65bbb1c3b423 100644
@@ -1,3 +1,5 @@
+:orphan:
+
  STM32F429 Overview
  ==================
 
Documentation/arm/stm32/stm32f746-overview.rst +2 -0
index b5f4b6ce7656..42d593085015 100644
@@ -1,3 +1,5 @@
+:orphan:
+
  STM32F746 Overview
  ==================
 
Documentation/arm/stm32/stm32f769-overview.rst +2 -0
index 228656ced2fe..f6adac862b17 100644
@@ -1,3 +1,5 @@
+:orphan:
+
  STM32F769 Overview
  ==================
 
Documentation/arm/stm32/stm32h743-overview.rst +2 -0
index 3458dc00095d..c525835e7473 100644
@@ -1,3 +1,5 @@
+:orphan:
+
  STM32H743 Overview
  ==================
 
Documentation/arm/stm32/stm32mp157-overview.rst +2 -0
index 62e176d47ca7..2c52cd020601 100644
@@ -1,3 +1,5 @@
+:orphan:
+
  STM32MP157 Overview
  ===================
 
Documentation/gpu/msm-crash-dump.rst +2 -0
index 757cd257e0d8..240ef200f76c 100644
@@ -1,3 +1,5 @@
+:orphan:
+
  =====================
  MSM Crash Dump Format
  =====================
Documentation/interconnect/interconnect.rst +2 -0
index c3e004893796..56e331dab70e 100644
@@ -1,5 +1,7 @@
  .. SPDX-License-Identifier: GPL-2.0
 
+:orphan:
+
  =====================================
  GENERIC SYSTEM INTERCONNECT SUBSYSTEM
  =====================================
Documentation/laptops/lg-laptop.rst +2 -0
index aa503ee9b3bc..f2c2ffe31101 100644
@@ -1,5 +1,7 @@
  .. SPDX-License-Identifier: GPL-2.0+
 
+:orphan:
+
  LG Gram laptop extra features
  =============================
 
Documentation/powerpc/isa-versions.rst +2 -0
index 812e20cc898c..66c24140ebf1 100644
@@ -1,3 +1,5 @@
+:orphan:
+
  CPU to ISA Version Mapping
  ==========================
 
Documentation/virtual/kvm/amd-memory-encryption.rst +2 -0
index 659bbc093b52..33d697ab8a58 100644
@@ -1,3 +1,5 @@
+:orphan:
+
  ======================================
  Secure Encrypted Virtualization (SEV)
  ======================================
Documentation/virtual/kvm/vcpu-requests.rst +2 -0
index 5feb3706a7ae..c1807a1b92e6 100644
@@ -1,3 +1,5 @@
+:orphan:
+
  =================
  KVM VCPU Requests
  =================
#16 lore raw

Re: [PATCH 09/22] docs: mark orphan documents as such

Em Mon, 3 Jun 2019 09:32:54 +0200
Christophe Leroy <[email protected]> escreveu:

Quoted 17 lines

Le 30/05/2019 à 01:23, Mauro Carvalho Chehab a écrit :

Quoted 16 lines

Sphinx doesn't like orphan documents:

Documentation/accelerators/ocxl.rst: WARNING: document isn't included in any toctree Documentation/arm/stm32/overview.rst: WARNING: document isn't included in any toctree Documentation/arm/stm32/stm32f429-overview.rst: WARNING: document isn't included in any toctree Documentation/arm/stm32/stm32f746-overview.rst: WARNING: document isn't included in any toctree Documentation/arm/stm32/stm32f769-overview.rst: WARNING: document isn't included in any toctree Documentation/arm/stm32/stm32h743-overview.rst: WARNING: document isn't included in any toctree Documentation/arm/stm32/stm32mp157-overview.rst: WARNING: document isn't included in any toctree Documentation/gpu/msm-crash-dump.rst: WARNING: document isn't included in any toctree Documentation/interconnect/interconnect.rst: WARNING: document isn't included in any toctree Documentation/laptops/lg-laptop.rst: WARNING: document isn't included in any toctree Documentation/powerpc/isa-versions.rst: WARNING: document isn't included in any toctree Documentation/virtual/kvm/amd-memory-encryption.rst: WARNING: document isn't included in any toctree Documentation/virtual/kvm/vcpu-requests.rst: WARNING: document isn't included in any toctree

Quoted 7 lines
Quoted 2 lines

So, while they aren't on any toctree, add :orphan: to them, in order to silent this warning.

Are those files really not meant to be included in a toctree ?

Shouldn't we include them in the relevant toctree instead of just shutting up Sphinx warnings ?

This is a good point. My understanding is that those orphaned docs are there for two reasons:

1) someone created a new document as .rst but there's no index.rst file yet, as there are lots of other documents already there not converted. That's the case, for example, of the ones under Documentation/arm;

2) They're part of an undergoing effort of converting stuff to ReST. One opted to keep it orphaned temporarily in order to avoid merge conflicts.

That's said, I have myself a big (/86 patches and growing) series with do a huge step on txt->rst conversion (it covers a significant amount of documentation). On this series, I'm removing the orphaned tags for several files (including, for example, those at Documentation/arm).

Yet, it is a lot easier to see if such series is not introducing warnings regressions if we first address those.

It should be notice that discovering the orphaned files should be as simple as:

git grep -l ":orphan:" Documentation

Quoted 148 lines

Christophe

Quoted 145 lines
---
  Documentation/accelerators/ocxl.rst                 | 2 ++
  Documentation/arm/stm32/overview.rst                | 2 ++
  Documentation/arm/stm32/stm32f429-overview.rst      | 2 ++
  Documentation/arm/stm32/stm32f746-overview.rst      | 2 ++
  Documentation/arm/stm32/stm32f769-overview.rst      | 2 ++
  Documentation/arm/stm32/stm32h743-overview.rst      | 2 ++
  Documentation/arm/stm32/stm32mp157-overview.rst     | 2 ++
  Documentation/gpu/msm-crash-dump.rst                | 2 ++
  Documentation/interconnect/interconnect.rst         | 2 ++
  Documentation/laptops/lg-laptop.rst                 | 2 ++
  Documentation/powerpc/isa-versions.rst              | 2 ++
  Documentation/virtual/kvm/amd-memory-encryption.rst | 2 ++
  Documentation/virtual/kvm/vcpu-requests.rst         | 2 ++
  13 files changed, 26 insertions(+)
Documentation/accelerators/ocxl.rst +2 -0
index 14cefc020e2d..b1cea19a90f5 100644
@@ -1,3 +1,5 @@
+:orphan:
+
  ========================================================
  OpenCAPI (Open Coherent Accelerator Processor Interface)
  ========================================================
Documentation/arm/stm32/overview.rst +2 -0
index 85cfc8410798..f7e734153860 100644
@@ -1,3 +1,5 @@
+:orphan:
+
  ========================
  STM32 ARM Linux Overview
  ========================
Documentation/arm/stm32/stm32f429-overview.rst +2 -0
index 18feda97f483..65bbb1c3b423 100644
@@ -1,3 +1,5 @@
+:orphan:
+
  STM32F429 Overview
  ==================
 
Documentation/arm/stm32/stm32f746-overview.rst +2 -0
index b5f4b6ce7656..42d593085015 100644
@@ -1,3 +1,5 @@
+:orphan:
+
  STM32F746 Overview
  ==================
 
Documentation/arm/stm32/stm32f769-overview.rst +2 -0
index 228656ced2fe..f6adac862b17 100644
@@ -1,3 +1,5 @@
+:orphan:
+
  STM32F769 Overview
  ==================
 
Documentation/arm/stm32/stm32h743-overview.rst +2 -0
index 3458dc00095d..c525835e7473 100644
@@ -1,3 +1,5 @@
+:orphan:
+
  STM32H743 Overview
  ==================
 
Documentation/arm/stm32/stm32mp157-overview.rst +2 -0
index 62e176d47ca7..2c52cd020601 100644
@@ -1,3 +1,5 @@
+:orphan:
+
  STM32MP157 Overview
  ===================
 
Documentation/gpu/msm-crash-dump.rst +2 -0
index 757cd257e0d8..240ef200f76c 100644
@@ -1,3 +1,5 @@
+:orphan:
+
  =====================
  MSM Crash Dump Format
  =====================
Documentation/interconnect/interconnect.rst +2 -0
index c3e004893796..56e331dab70e 100644
@@ -1,5 +1,7 @@
  .. SPDX-License-Identifier: GPL-2.0
 
+:orphan:
+
  =====================================
  GENERIC SYSTEM INTERCONNECT SUBSYSTEM
  =====================================
Documentation/laptops/lg-laptop.rst +2 -0
index aa503ee9b3bc..f2c2ffe31101 100644
@@ -1,5 +1,7 @@
  .. SPDX-License-Identifier: GPL-2.0+
 
+:orphan:
+
  LG Gram laptop extra features
  =============================
 
Documentation/powerpc/isa-versions.rst +2 -0
index 812e20cc898c..66c24140ebf1 100644
@@ -1,3 +1,5 @@
+:orphan:
+
  CPU to ISA Version Mapping
  ==========================
 
Documentation/virtual/kvm/amd-memory-encryption.rst +2 -0
index 659bbc093b52..33d697ab8a58 100644
@@ -1,3 +1,5 @@
+:orphan:
+
  ======================================
  Secure Encrypted Virtualization (SEV)
  ======================================
Documentation/virtual/kvm/vcpu-requests.rst +0 -1
index 5feb3706a7ae..c1807a1b92e6 100644
--- a/Documentation/virtual/kvm/vcpu-requests.rst
Quoted 8 lines

Documentation/virtual/kvm/vcpu-requests.rst line 5

Quoted 8 lines

+++ b/Documentation/virtual/kvm/vcpu-requests.rst

Documentation/virtual/kvm/vcpu-requests.rst +2 -0
@@ -1,3 +1,5 @@
+:orphan:
+
  =================
  KVM VCPU Requests
  =================

Thanks,
Mauro

_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

#17 lore raw

PATCH 10/22 docs: amd-memory-encryption.rst get rid of warnings

In reply to Mauro Carvalho Chehab

Get rid of those warnings:

Documentation/virtual/kvm/amd-memory-encryption.rst:244: WARNING: Citation [white-paper] is not referenced. Documentation/virtual/kvm/amd-memory-encryption.rst:246: WARNING: Citation [amd-apm] is not referenced. Documentation/virtual/kvm/amd-memory-encryption.rst:247: WARNING: Citation [kvm-forum] is not referenced.

For references that aren't mentioned at the text by adding an explicit reference to them.

---
 Documentation/virtual/kvm/amd-memory-encryption.rst | 3 +++
 1 file changed, 3 insertions(+)
Documentation/virtual/kvm/amd-memory-encryption.rst +3 -0
index 33d697ab8a58..6c37ff9a0a3c 100644
@@ -243,6 +243,9 @@ Returns: 0 on success, -negative on error
 References
 ==========
 
+
+See [white-paper]_, [api-spec]_, [amd-apm]_ and [kvm-forum]_ for more info.
+
 .. [white-paper] http://amd-dev.wpengine.netdna-cdn.com/wordpress/media/2013/12/AMD_Memory_Encryption_Whitepaper_v7-Public.pdf
 .. [api-spec] http://support.amd.com/TechDocs/55766_SEV-KM_API_Specification.pdf
 .. [amd-apm] http://support.amd.com/TechDocs/24593.pdf (section 15.34)
Signature · 1 line
2.21.0
maintainer Acked-by on v1 10/22
#18 lore raw

Re: [PATCH 10/22] docs: amd-memory-encryption.rst get rid of warnings

Quoted 20 lines · Mauro Carvalho Chehab

Get rid of those warnings:

Documentation/virtual/kvm/amd-memory-encryption.rst:244: WARNING: Citation [white-paper] is not referenced. Documentation/virtual/kvm/amd-memory-encryption.rst:246: WARNING: Citation [amd-apm] is not referenced. Documentation/virtual/kvm/amd-memory-encryption.rst:247: WARNING: Citation [kvm-forum] is not referenced.

For references that aren't mentioned at the text by adding an explicit reference to them.

---
 Documentation/virtual/kvm/amd-memory-encryption.rst | 3 +++
 1 file changed, 3 insertions(+)
Documentation/virtual/kvm/amd-memory-encryption.rst +0 -0
index 33d697ab8a58..6c37ff9a0a3c 100644

Documentation/virtual/kvm/amd-memory-encryption.rst Returns: 0 on success, -negative on error · line 251

Quoted 9 lines
Documentation/virtual/kvm/amd-memory-encryption.rst +3 -0
@@ -243,6 +243,9 @@ Returns: 0 on success, -negative on error
 References
 ==========
 
+
+See [white-paper]_, [api-spec]_, [amd-apm]_ and [kvm-forum]_ for more info.
+
 .. [white-paper] http://amd-dev.wpengine.netdna-cdn.com/wordpress/media/2013/12/AMD_Memory_Encryption_Whitepaper_v7-Public.pdf
 .. [api-spec] http://support.amd.com/TechDocs/55766_SEV-KM_API_Specification.pdf
 .. [amd-apm] http://support.amd.com/TechDocs/24593.pdf (section 15.34)
#19 lore raw

PATCH 11/22 gpu: amdgpu: fix broken amdgpu_dma_buf.c references

In reply to Mauro Carvalho Chehab

This file was renamed, but docs weren't updated accordingly.

WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -function PRIME Buffer Sharing ./drivers/gpu/drm/amd/amdgpu/amdgpu_prime.c' failed with return code 1
WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -internal ./drivers/gpu/drm/amd/amdgpu/amdgpu_prime.c' failed with return code 2

Fixes 988076cd8c5c ("drm/amdgpu: rename amdgpu_prime.[ch] into amdgpu_dma_buf.[ch]")
---
 Documentation/gpu/amdgpu.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
Documentation/gpu/amdgpu.rst +2 -2
index a740e491dfcc..a15199b1b02e 100644
@@ -37,10 +37,10 @@ Buffer Objects
 PRIME Buffer Sharing
 --------------------
 
-.. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_prime.c
+.. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c
    :doc: PRIME Buffer Sharing
 
-.. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_prime.c
+.. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c
    :internal:
 
 MMU Notifier
Signature · 6 lines
2.21.0

_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Reviewed-by on v1 11/22
#20 lore raw

Re: [PATCH 11/22] gpu: amdgpu: fix broken amdgpu_dma_buf.c references

Am 30.05.19 um 01:23 schrieb Mauro Carvalho Chehab:

Quoted 7 lines

This file was renamed, but docs weren't updated accordingly.

WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -function PRIME Buffer Sharing ./drivers/gpu/drm/amd/amdgpu/amdgpu_prime.c' failed with return code 1
WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -internal ./drivers/gpu/drm/amd/amdgpu/amdgpu_prime.c' failed with return code 2

Fixes 988076cd8c5c ("drm/amdgpu: rename amdgpu_prime.[ch] into amdgpu_dma_buf.[ch]")
Quoted 21 lines
---
  Documentation/gpu/amdgpu.rst | 4 ++--
  1 file changed, 2 insertions(+), 2 deletions(-)
Documentation/gpu/amdgpu.rst +2 -2
index a740e491dfcc..a15199b1b02e 100644
@@ -37,10 +37,10 @@ Buffer Objects
  PRIME Buffer Sharing
  --------------------
 
-.. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_prime.c
+.. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c
     :doc: PRIME Buffer Sharing
 
-.. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_prime.c
+.. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c
     :internal:
 
  MMU Notifier
Applied
#21 lore raw

Re: [PATCH 11/22] gpu: amdgpu: fix broken amdgpu_dma_buf.c references

Quoted 4 lines · Christian König

Am 30.05.19 um 01:23 schrieb Mauro Carvalho Chehab:

Quoted 2 lines

This file was renamed, but docs weren't updated accordingly.

Quoted 8 lines
Quoted 5 lines

WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -function PRIME Buffer Sharing ./drivers/gpu/drm/amd/amdgpu/amdgpu_prime.c' failed with return code 1
WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -internal ./drivers/gpu/drm/amd/amdgpu/amdgpu_prime.c' failed with return code 2

Fixes 988076cd8c5c ("drm/amdgpu: rename amdgpu_prime.[ch] into amdgpu_dma_buf.[ch]")

Applied. thanks!

Alex

Quoted 26 lines
Quoted 11 lines
---
  Documentation/gpu/amdgpu.rst | 4 ++--
  1 file changed, 2 insertions(+), 2 deletions(-)
Documentation/gpu/amdgpu.rst +0 -0
index a740e491dfcc..a15199b1b02e 100644
@@ -37,10 +37,10 @@ Buffer Objects
  PRIME Buffer Sharing
  --------------------

Documentation/gpu/amdgpu.rst Buffer Objects · line 46

Quoted 10 lines
Documentation/gpu/amdgpu.rst +2 -2
 
-.. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_prime.c
+.. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c
     :doc: PRIME Buffer Sharing
 
-.. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_prime.c
+.. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c
     :internal:
 
  MMU Notifier

_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel

#22 lore raw

PATCH 12/22 gpu: i915.rst: Fix references to renamed files

In reply to Mauro Carvalho Chehab

WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -function Hardware workarounds ./drivers/gpu/drm/i915/intel_workarounds.c' failed with return code 1
WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -function Logical Rings, Logical Ring Contexts and Execlists ./drivers/gpu/drm/i915/intel_lrc.c' failed with return code 1
WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -internal ./drivers/gpu/drm/i915/intel_lrc.c' failed with return code 2

Fixes 112ed2d31a46 ("drm/i915: Move GraphicsTechnology files under gt/")
---
 Documentation/gpu/i915.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
Documentation/gpu/i915.rst +3 -3
index 055df45596c1..38fefeb99bba 100644
@@ -61,7 +61,7 @@ Intel GVT-g Host Support(vGPU device model)
 Workarounds
 -----------
 
-.. kernel-doc:: drivers/gpu/drm/i915/intel_workarounds.c
+.. kernel-doc:: drivers/gpu/drm/i915/gt/selftest_workarounds.c
    :doc: Hardware workarounds
 
 Display Hardware Handling
@@ -379,10 +379,10 @@ User Batchbuffer Execution
 Logical Rings, Logical Ring Contexts and Execlists
 --------------------------------------------------
 
-.. kernel-doc:: drivers/gpu/drm/i915/intel_lrc.c
+.. kernel-doc:: drivers/gpu/drm/i915/gt/intel_lrc.c
    :doc: Logical Rings, Logical Ring Contexts and Execlists
 
-.. kernel-doc:: drivers/gpu/drm/i915/intel_lrc.c
+.. kernel-doc:: drivers/gpu/drm/i915/gt/intel_lrc.c
    :internal:
 
 Global GTT views
Signature · 6 lines
2.21.0

_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
maintainer
#23 lore raw

Re: [PATCH 12/22] gpu: i915.rst: Fix references to renamed files

Quoted 15 lines · Mauro Carvalho Chehab

WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -function Hardware workarounds ./drivers/gpu/drm/i915/intel_workarounds.c' failed with return code 1
WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -function Logical Rings, Logical Ring Contexts and Execlists ./drivers/gpu/drm/i915/intel_lrc.c' failed with return code 1
WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -internal ./drivers/gpu/drm/i915/intel_lrc.c' failed with return code 2

Fixes 112ed2d31a46 ("drm/i915: Move GraphicsTechnology files under gt/")
---
 Documentation/gpu/i915.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
Documentation/gpu/i915.rst +0 -0
index 055df45596c1..38fefeb99bba 100644

Documentation/gpu/i915.rst Intel GVT-g Host Support(vGPU device model) · line 65

Quoted 6 lines
Documentation/gpu/i915.rst +1 -1
@@ -61,7 +61,7 @@ Intel GVT-g Host Support(vGPU device model)
 Workarounds
 -----------
 
-.. kernel-doc:: drivers/gpu/drm/i915/intel_workarounds.c
+.. kernel-doc:: drivers/gpu/drm/i915/gt/selftest_workarounds.c
    :doc: Hardware workarounds

Thanks for the patch. The basename should remain the same here.

I can pick up the updated version via drm-intel.

BR,
Jani.

Quoted 15 lines
Documentation/gpu/i915.rst +2 -2
 Display Hardware Handling
@@ -379,10 +379,10 @@ User Batchbuffer Execution
 Logical Rings, Logical Ring Contexts and Execlists
 --------------------------------------------------
 
-.. kernel-doc:: drivers/gpu/drm/i915/intel_lrc.c
+.. kernel-doc:: drivers/gpu/drm/i915/gt/intel_lrc.c
    :doc: Logical Rings, Logical Ring Contexts and Execlists
 
-.. kernel-doc:: drivers/gpu/drm/i915/intel_lrc.c
+.. kernel-doc:: drivers/gpu/drm/i915/gt/intel_lrc.c
    :internal:
 
 Global GTT views
Signature · 1 line
Jani Nikula, Intel Open Source Graphics Center
maintainer
#24 lore raw

Re: [PATCH 12/22] gpu: i915.rst: Fix references to renamed files

In reply to Mauro Carvalho Chehab

Quoting Mauro Carvalho Chehab (2019-05-30 02:23:43)

Quoted 15 lines

WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -function Hardware workarounds ./drivers/gpu/drm/i915/intel_workarounds.c' failed with return code 1
WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -function Logical Rings, Logical Ring Contexts and Execlists ./drivers/gpu/drm/i915/intel_lrc.c' failed with return code 1
WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -internal ./drivers/gpu/drm/i915/intel_lrc.c' failed with return code 2

Fixes 112ed2d31a46 ("drm/i915: Move GraphicsTechnology files under gt/")
---
 Documentation/gpu/i915.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
Documentation/gpu/i915.rst +0 -0
index 055df45596c1..38fefeb99bba 100644

Documentation/gpu/i915.rst Intel GVT-g Host Support(vGPU device model) · line 64

Quoted 5 lines
Documentation/gpu/i915.rst +1 -1
@@ -61,7 +61,7 @@ Intel GVT-g Host Support(vGPU device model)
 Workarounds
 -----------
 
-.. kernel-doc:: drivers/gpu/drm/i915/intel_workarounds.c
+.. kernel-doc:: drivers/gpu/drm/i915/gt/selftest_workarounds.c

This should be gt/intel_workarounds.c

Do you want me to merge this, or do you plan on merging through documentation tree?

Regards, Joonas
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

#25 lore raw

PATCH 13/22 docs: zh_CN: avoid duplicate citation references

In reply to Mauro Carvalho Chehab

Documentation/process/management-style.rst:35: WARNING: duplicate label decisions, other instance in Documentation/translations/zh_CN/process/management-style.rst
Documentation/process/programming-language.rst:37: WARNING: duplicate citation c-language, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:38: WARNING: duplicate citation gcc, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:39: WARNING: duplicate citation clang, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:40: WARNING: duplicate citation icc, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:41: WARNING: duplicate citation gcc-c-dialect-options, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:42: WARNING: duplicate citation gnu-extensions, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:43: WARNING: duplicate citation gcc-attribute-syntax, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:44: WARNING: duplicate citation n2049, other instance in Documentation/translations/zh_CN/process/programming-language.rst

---
 .../zh_CN/process/management-style.rst        |  4 +--
 .../zh_CN/process/programming-language.rst    | 28 +++++++++----------
 2 files changed, 16 insertions(+), 16 deletions(-)
Documentation/translations/zh_CN/process/management-style.rst +2 -2
index a181fa56d19e..c6a5bb285797 100644
@@ -28,7 +28,7 @@ Linux内核管理风格
 
 不管怎样,这里是:
 
-.. _decisions:
+.. _cn_decisions:
 
 1)决策
 -------
@@ -108,7 +108,7 @@ Linux内核管理风格
 但是,为了做好作为内核管理者的准备,最好记住不要烧掉任何桥梁,不要轰炸任何
 无辜的村民,也不要疏远太多的内核开发人员。事实证明,疏远人是相当容易的,而
 亲近一个疏远的人是很难的。因此,“疏远”立即属于“不可逆”的范畴,并根据
-:ref:`decisions` 成为绝不可以做的事情。
+:ref:`cn_decisions` 成为绝不可以做的事情。
 
 这里只有几个简单的规则:
 
Documentation/translations/zh_CN/process/programming-language.rst +14 -14
index 51fd4ef48ea1..9de9a3108c4d 100644
@@ -8,21 +8,21 @@
 程序设计语言
 ============
 
-内核是用C语言 [c-language]_ 编写的。更准确地说,内核通常是用 ``gcc`` [gcc]_
-在 ``-std=gnu89`` [gcc-c-dialect-options]_ 下编译的:ISO C90的 GNU 方言(
+内核是用C语言 [cn_c-language]_ 编写的。更准确地说,内核通常是用 ``gcc`` [cn_gcc]_
+在 ``-std=gnu89`` [cn_gcc-c-dialect-options]_ 下编译的:ISO C90的 GNU 方言(
 包括一些C99特性)
 
-这种方言包含对语言 [gnu-extensions]_ 的许多扩展,当然,它们许多都在内核中使用。
+这种方言包含对语言 [cn_gnu-extensions]_ 的许多扩展,当然,它们许多都在内核中使用。
 
-对于一些体系结构,有一些使用 ``clang`` [clang]_ 和 ``icc`` [icc]_ 编译内核
+对于一些体系结构,有一些使用 ``clang`` [cn_clang]_ 和 ``icc`` [cn_icc]_ 编译内核
 的支持,尽管在编写此文档时还没有完成,仍需要第三方补丁。
 
 属性
 ----
 
-在整个内核中使用的一个常见扩展是属性(attributes) [gcc-attribute-syntax]_
+在整个内核中使用的一个常见扩展是属性(attributes) [cn_gcc-attribute-syntax]_
 属性允许将实现定义的语义引入语言实体(如变量、函数或类型),而无需对语言进行
-重大的语法更改(例如添加新关键字) [n2049]_
+重大的语法更改(例如添加新关键字) [cn_n2049]_
 
 在某些情况下,属性是可选的(即不支持这些属性的编译器仍然应该生成正确的代码,
 即使其速度较慢或执行的编译时检查/诊断次数不够)
@@ -31,11 +31,11 @@
 ``__attribute__((__pure__))`` ),以检测可以使用哪些关键字和/或缩短代码, 具体
 请参阅 ``include/linux/compiler_attributes.h``
 
-.. [c-language] http://www.open-std.org/jtc1/sc22/wg14/www/standards
-.. [gcc] https://gcc.gnu.org
-.. [clang] https://clang.llvm.org
-.. [icc] https://software.intel.com/en-us/c-compilers
-.. [gcc-c-dialect-options] https://gcc.gnu.org/onlinedocs/gcc/C-Dialect-Options.html
-.. [gnu-extensions] https://gcc.gnu.org/onlinedocs/gcc/C-Extensions.html
-.. [gcc-attribute-syntax] https://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html
-.. [n2049] http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2049.pdf
+.. [cn_c-language] http://www.open-std.org/jtc1/sc22/wg14/www/standards
+.. [cn_gcc] https://gcc.gnu.org
+.. [cn_clang] https://clang.llvm.org
+.. [cn_icc] https://software.intel.com/en-us/c-compilers
+.. [cn_gcc-c-dialect-options] https://gcc.gnu.org/onlinedocs/gcc/C-Dialect-Options.html
+.. [cn_gnu-extensions] https://gcc.gnu.org/onlinedocs/gcc/C-Extensions.html
+.. [cn_gcc-attribute-syntax] https://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html
+.. [cn_n2049] http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2049.pdf
Signature · 1 line
2.21.0
#26 lore raw

Re: [PATCH 13/22] docs: zh_CN: avoid duplicate citation references

Quoted 30 lines · Mauro Carvalho Chehab

Documentation/process/management-style.rst:35: WARNING: duplicate label decisions, other instance in Documentation/translations/zh_CN/process/management-style.rst
Documentation/process/programming-language.rst:37: WARNING: duplicate citation c-language, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:38: WARNING: duplicate citation gcc, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:39: WARNING: duplicate citation clang, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:40: WARNING: duplicate citation icc, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:41: WARNING: duplicate citation gcc-c-dialect-options, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:42: WARNING: duplicate citation gnu-extensions, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:43: WARNING: duplicate citation gcc-attribute-syntax, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:44: WARNING: duplicate citation n2049, other instance in Documentation/translations/zh_CN/process/programming-language.rst

---
 .../zh_CN/process/management-style.rst        |  4 +--
 .../zh_CN/process/programming-language.rst    | 28 +++++++++----------
 2 files changed, 16 insertions(+), 16 deletions(-)
Documentation/translations/zh_CN/process/management-style.rst +1 -1
index a181fa56d19e..c6a5bb285797 100644
@@ -28,7 +28,7 @@ Linux内核管理风格
 
 不管怎样,这里是:
 
-.. _decisions:
+.. _cn_decisions:
 
 1)决策
 -------

Documentation/translations/zh_CN/process/management-style.rst Linux内核管理风格 · line 111

Quoted 5 lines
Documentation/translations/zh_CN/process/management-style.rst +1 -1
@@ -108,7 +108,7 @@ Linux内核管理风格
 但是,为了做好作为内核管理者的准备,最好记住不要烧掉任何桥梁,不要轰炸任何
 无辜的村民,也不要疏远太多的内核开发人员。事实证明,疏远人是相当容易的,而
 亲近一个疏远的人是很难的。因此,“疏远”立即属于“不可逆”的范畴,并根据
-:ref:`decisions` 成为绝不可以做的事情。
+:ref:`cn_decisions` 成为绝不可以做的事情。

It's good to have.

Quoted 8 lines
Documentation/translations/zh_CN/process/management-style.rst +0 -0
 这里只有几个简单的规则:
 
Documentation/translations/zh_CN/process/programming-language.rst +0 -0
index 51fd4ef48ea1..9de9a3108c4d 100644

Documentation/translations/zh_CN/process/programming-language.rst line 11

Quoted 6 lines
Documentation/translations/zh_CN/process/programming-language.rst +1 -2
@@ -8,21 +8,21 @@
 程序设计语言
 ============
 
-内核是用C语言 [c-language]_ 编写的。更准确地说,内核通常是用 ``gcc`` [gcc]_
-在 ``-std=gnu89`` [gcc-c-dialect-options]_ 下编译的:ISO C90的 GNU 方言(
+内核是用C语言 [cn_c-language]_ 编写的。更准确地说,内核通常是用 ``gcc`` [cn_gcc]_

this change isn't good. cn_gcc will show in docs, it looks wired and confusing for peoples. other changes have the same issue. Could you find other way to fix the warning? or I'd rather tolerant it.

Thanks
Alex

#27 lore raw

Re: [PATCH 13/22] docs: zh_CN: avoid duplicate citation references

Em Sun, 2 Jun 2019 23:01:21 +0800
Alex Shi <[email protected]> escreveu:

Quoted 50 lines · Mauro Carvalho Chehab
Quoted 30 lines

Documentation/process/management-style.rst:35: WARNING: duplicate label decisions, other instance in Documentation/translations/zh_CN/process/management-style.rst
Documentation/process/programming-language.rst:37: WARNING: duplicate citation c-language, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:38: WARNING: duplicate citation gcc, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:39: WARNING: duplicate citation clang, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:40: WARNING: duplicate citation icc, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:41: WARNING: duplicate citation gcc-c-dialect-options, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:42: WARNING: duplicate citation gnu-extensions, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:43: WARNING: duplicate citation gcc-attribute-syntax, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:44: WARNING: duplicate citation n2049, other instance in Documentation/translations/zh_CN/process/programming-language.rst

---
 .../zh_CN/process/management-style.rst        |  4 +--
 .../zh_CN/process/programming-language.rst    | 28 +++++++++----------
 2 files changed, 16 insertions(+), 16 deletions(-)
Documentation/translations/zh_CN/process/management-style.rst +1 -1
index a181fa56d19e..c6a5bb285797 100644
@@ -28,7 +28,7 @@ Linux内核管理风格
 
 不管怎样,这里是:
 
-.. _decisions:
+.. _cn_decisions:
 
 1)决策
 -------

Documentation/translations/zh_CN/process/management-style.rst Linux内核管理风格 · line 111

Quoted 5 lines
Documentation/translations/zh_CN/process/management-style.rst +1 -1
@@ -108,7 +108,7 @@ Linux内核管理风格
 但是,为了做好作为内核管理者的准备,最好记住不要烧掉任何桥梁,不要轰炸任何
 无辜的村民,也不要疏远太多的内核开发人员。事实证明,疏远人是相当容易的,而
 亲近一个疏远的人是很难的。因此,“疏远”立即属于“不可逆”的范畴,并根据
-:ref:`decisions` 成为绝不可以做的事情。
+:ref:`cn_decisions` 成为绝不可以做的事情。  

It's good to have.

Quoted 11 lines
Documentation/translations/zh_CN/process/management-style.rst +0 -0
 这里只有几个简单的规则:
 
Documentation/translations/zh_CN/process/programming-language.rst +0 -0
index 51fd4ef48ea1..9de9a3108c4d 100644
@@ -8,21 +8,21 @@
 程序设计语言
 ============
 
Quoted 5 lines

Documentation/translations/zh_CN/process/programming-language.rst line 11

Quoted 3 lines
Documentation/translations/zh_CN/process/programming-language.rst +1 -2
-内核是用C语言 [c-language]_ 编写的。更准确地说,内核通常是用 ``gcc`` [gcc]_
-在 ``-std=gnu89`` [gcc-c-dialect-options]_ 下编译的:ISO C90的 GNU 方言(
+内核是用C语言 [cn_c-language]_ 编写的。更准确地说,内核通常是用 ``gcc`` [cn_gcc]_  

this change isn't good. cn_gcc will show in docs, it looks wired and confusing for peoples. other changes have the same issue. Could you find other way to fix the warning? or I'd rather tolerant it.

Well, Sphinx has a way to do that, like, for example:

Documentation/translations/zh_CN/process/programming-language.rst +1 -1
index 9de9a3108c4d..353fb8eaf4b5 100644
@@ -9,7 +9,7 @@
 ============
 
 内核是用C语言 [cn_c-language]_ 编写的。更准确地说,内核通常是用 ``gcc`` [cn_gcc]_
-在 ``-std=gnu89`` [cn_gcc-c-dialect-options]_ 下编译的:ISO C90的 GNU 方言(
+在 ``-std=gnu89`` :ref:`gcc C dialect options <cn_gcc-c-dialect-options>` 下编译的:ISO C90的 GNU 方言(
 包括一些C99特性)
 
 这种方言包含对语言 [cn_gnu-extensions]_ 的许多扩展,当然,它们许多都在内核中使用。

If we use that, at least for some of those references, it would probably be better to translate "dialect-options" (and similar terms) to Chinese.

Thanks,
Mauro

#28 lore raw

Re: [PATCH 13/22] docs: zh_CN: avoid duplicate citation references

Em Tue, 4 Jun 2019 07:20:57 -0300
Mauro Carvalho Chehab <[email protected]> escreveu:

Quoted 75 lines

Em Sun, 2 Jun 2019 23:01:21 +0800
Alex Shi <[email protected]> escreveu:

Quoted 50 lines · Mauro Carvalho Chehab
Quoted 30 lines

Documentation/process/management-style.rst:35: WARNING: duplicate label decisions, other instance in Documentation/translations/zh_CN/process/management-style.rst
Documentation/process/programming-language.rst:37: WARNING: duplicate citation c-language, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:38: WARNING: duplicate citation gcc, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:39: WARNING: duplicate citation clang, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:40: WARNING: duplicate citation icc, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:41: WARNING: duplicate citation gcc-c-dialect-options, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:42: WARNING: duplicate citation gnu-extensions, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:43: WARNING: duplicate citation gcc-attribute-syntax, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:44: WARNING: duplicate citation n2049, other instance in Documentation/translations/zh_CN/process/programming-language.rst

---
 .../zh_CN/process/management-style.rst        |  4 +--
 .../zh_CN/process/programming-language.rst    | 28 +++++++++----------
 2 files changed, 16 insertions(+), 16 deletions(-)
Documentation/translations/zh_CN/process/management-style.rst +1 -1
index a181fa56d19e..c6a5bb285797 100644
@@ -28,7 +28,7 @@ Linux内核管理风格
 
 不管怎样,这里是:
 
-.. _decisions:
+.. _cn_decisions:
 
 1)决策
 -------

Documentation/translations/zh_CN/process/management-style.rst Linux内核管理风格 · line 111

Quoted 5 lines
Documentation/translations/zh_CN/process/management-style.rst +1 -1
@@ -108,7 +108,7 @@ Linux内核管理风格
 但是,为了做好作为内核管理者的准备,最好记住不要烧掉任何桥梁,不要轰炸任何
 无辜的村民,也不要疏远太多的内核开发人员。事实证明,疏远人是相当容易的,而
 亲近一个疏远的人是很难的。因此,“疏远”立即属于“不可逆”的范畴,并根据
-:ref:`decisions` 成为绝不可以做的事情。
+:ref:`cn_decisions` 成为绝不可以做的事情。    

It's good to have.

Quoted 11 lines
Documentation/translations/zh_CN/process/management-style.rst +0 -0
 这里只有几个简单的规则:
 
Documentation/translations/zh_CN/process/programming-language.rst +0 -0
index 51fd4ef48ea1..9de9a3108c4d 100644
@@ -8,21 +8,21 @@
 程序设计语言
 ============
 
Quoted 5 lines

Documentation/translations/zh_CN/process/programming-language.rst line 11

Quoted 3 lines
Documentation/translations/zh_CN/process/programming-language.rst +1 -2
-内核是用C语言 [c-language]_ 编写的。更准确地说,内核通常是用 ``gcc`` [gcc]_
-在 ``-std=gnu89`` [gcc-c-dialect-options]_ 下编译的:ISO C90的 GNU 方言(
+内核是用C语言 [cn_c-language]_ 编写的。更准确地说,内核通常是用 ``gcc`` [cn_gcc]_    

this change isn't good. cn_gcc will show in docs, it looks wired and confusing for peoples. other changes have the same issue. Could you find other way to fix the warning? or I'd rather tolerant it.

Well, Sphinx has a way to do that, like, for example:

Documentation/translations/zh_CN/process/programming-language.rst +1 -1
index 9de9a3108c4d..353fb8eaf4b5 100644
@@ -9,7 +9,7 @@
 ============
 
 内核是用C语言 [cn_c-language]_ 编写的。更准确地说,内核通常是用 ``gcc`` [cn_gcc]_
-在 ``-std=gnu89`` [cn_gcc-c-dialect-options]_ 下编译的:ISO C90的 GNU 方言(
+在 ``-std=gnu89`` :ref:`gcc C dialect options <cn_gcc-c-dialect-options>` 下编译的:ISO C90的 GNU 方言(
 包括一些C99特性)
 
 这种方言包含对语言 [cn_gnu-extensions]_ 的许多扩展,当然,它们许多都在内核中使用。
Quoted 5 lines

If we use that, at least for some of those references, it would probably be better to translate "dialect-options" (and similar terms) to Chinese.

Thanks,
Mauro

Thanks,
Mauro

This should do the work:

[PATCH] docs: zh_CN: avoid duplicate citation references

Documentation/process/management-style.rst:35: WARNING: duplicate label decisions, other instance in Documentation/translations/zh_CN/process/management-style.rst
Documentation/process/programming-language.rst:37: WARNING: duplicate citation c-language, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:38: WARNING: duplicate citation gcc, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:39: WARNING: duplicate citation clang, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:40: WARNING: duplicate citation icc, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:41: WARNING: duplicate citation gcc-c-dialect-options, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:42: WARNING: duplicate citation gnu-extensions, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:43: WARNING: duplicate citation gcc-attribute-syntax, other instance in Documentation/translations/zh_CN/process/programming-language.rst
Documentation/process/programming-language.rst:44: WARNING: duplicate citation n2049, other instance in Documentation/translations/zh_CN/process/programming-language.rst

Documentation/translations/zh_CN/process/management-style.rst +2 -2
index a181fa56d19e..c6a5bb285797 100644
@@ -28,7 +28,7 @@ Linux内核管理风格
 
 不管怎样,这里是:
 
-.. _decisions:
+.. _cn_decisions:
 
 1)决策
 -------
@@ -108,7 +108,7 @@ Linux内核管理风格
 但是,为了做好作为内核管理者的准备,最好记住不要烧掉任何桥梁,不要轰炸任何
 无辜的村民,也不要疏远太多的内核开发人员。事实证明,疏远人是相当容易的,而
 亲近一个疏远的人是很难的。因此,“疏远”立即属于“不可逆”的范畴,并根据
-:ref:`decisions` 成为绝不可以做的事情。
+:ref:`cn_decisions` 成为绝不可以做的事情。
 
 这里只有几个简单的规则:
 
Documentation/translations/zh_CN/process/programming-language.rst +45 -14

77 lines not on this page · raw message

#29 lore raw

PATCH 14/22 docs: vm: hmm.rst: fix some warnings

In reply to Mauro Carvalho Chehab

Documentation/vm/hmm.rst:292: WARNING: Unexpected indentation. Documentation/vm/hmm.rst:300: WARNING: Unexpected indentation.

---
 Documentation/vm/hmm.rst | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)
Documentation/vm/hmm.rst +6 -3
index ec1efa32af3c..1ab609ca7835 100644
@@ -283,12 +283,14 @@ The hmm_range struct has 2 fields default_flags and pfn_flags_mask that allows
 to set fault or snapshot policy for a whole range instead of having to set them
 for each entries in the range.
 
-For instance if the device flags for device entries are:
+For instance if the device flags for device entries are::
+
     VALID (1 << 63)
     WRITE (1 << 62)
 
 Now let say that device driver wants to fault with at least read a range then
-it does set:
+it does set::
+
     range->default_flags = (1 << 63)
     range->pfn_flags_mask = 0;
 
@@ -296,7 +298,8 @@ and calls hmm_range_fault() as described above. This will fill fault all page
 in the range with at least read permission.
 
 Now let say driver wants to do the same except for one page in the range for
-which its want to have write. Now driver set:
+which its want to have write. Now driver set::
+
     range->default_flags = (1 << 63);
     range->pfn_flags_mask = (1 << 62);
     range->pfns[index_of_write] = (1 << 62);
Signature · 1 line
2.21.0
#30 lore raw

PATCH 15/22 docs: it: license-rules.rst: get rid of warnings

In reply to Mauro Carvalho Chehab

There's a wrong identation on a code block, and it tries to use a reference that was not defined at the Italian translation.

Documentation/translations/it_IT/process/license-rules.rst:329: WARNING: Literal block expected; none found. Documentation/translations/it_IT/process/license-rules.rst:332: WARNING: Unexpected indentation. Documentation/translations/it_IT/process/license-rules.rst:339: WARNING: Block quote ends without a blank line; unexpected unindent. Documentation/translations/it_IT/process/license-rules.rst:341: WARNING: Unexpected indentation. Documentation/translations/it_IT/process/license-rules.rst:305: WARNING: Unknown target name: "metatags".

---
 .../it_IT/process/license-rules.rst           | 28 +++++++++----------
 1 file changed, 14 insertions(+), 14 deletions(-)
Documentation/translations/it_IT/process/license-rules.rst +14 -14
index f058e06996dc..06abeb7dd307 100644
@@ -303,7 +303,7 @@ essere categorizzate in:
      LICENSES/dual
 
    I file in questa cartella contengono il testo completo della rispettiva
-   licenza e i suoi `Metatags`_.  I nomi dei file sono identici agli
+   licenza e i suoi `Metatags`.  I nomi dei file sono identici agli
    identificatori di licenza SPDX che dovrebbero essere usati nei file
    sorgenti.
 
@@ -326,19 +326,19 @@ essere categorizzate in:
 
    Esempio del formato del file::
 
-   Valid-License-Identifier: MPL-1.1
-   SPDX-URL: https://spdx.org/licenses/MPL-1.1.html
-   Usage-Guide:
-     Do NOT use. The MPL-1.1 is not GPL2 compatible. It may only be used for
-     dual-licensed files where the other license is GPL2 compatible.
-     If you end up using this it MUST be used together with a GPL2 compatible
-     license using "OR".
-     To use the Mozilla Public License version 1.1 put the following SPDX
-     tag/value pair into a comment according to the placement guidelines in
-     the licensing rules documentation:
-   SPDX-License-Identifier: MPL-1.1
-   License-Text:
-     Full license text
+    Valid-License-Identifier: MPL-1.1
+    SPDX-URL: https://spdx.org/licenses/MPL-1.1.html
+    Usage-Guide:
+      Do NOT use. The MPL-1.1 is not GPL2 compatible. It may only be used for
+      dual-licensed files where the other license is GPL2 compatible.
+      If you end up using this it MUST be used together with a GPL2 compatible
+      license using "OR".
+      To use the Mozilla Public License version 1.1 put the following SPDX
+      tag/value pair into a comment according to the placement guidelines in
+      the licensing rules documentation:
+    SPDX-License-Identifier: MPL-1.1
+    License-Text:
+      Full license text
 
 |
 
Signature · 1 line
2.21.0
maintainer
#31 lore raw

Re: [PATCH 15/22] docs: it: license-rules.rst: get rid of warnings

Quoted 25 lines · CEST Mauro Carvalho Chehab

There's a wrong identation on a code block, and it tries to use a reference that was not defined at the Italian translation.

Documentation/translations/it_IT/process/license-rules.rst:329: WARNING:
Literal block expected; none found. Documentation/translations/it_IT/process/license-rules.rst:332: WARNING:
Unexpected indentation. Documentation/translations/it_IT/process/license-rules.rst:339: WARNING:
Block quote ends without a blank line; unexpected unindent. Documentation/translations/it_IT/process/license-rules.rst:341: WARNING:
Unexpected indentation. Documentation/translations/it_IT/process/license-rules.rst:305: WARNING:
Unknown target name: "metatags".

---
 .../it_IT/process/license-rules.rst           | 28 +++++++++----------
 1 file changed, 14 insertions(+), 14 deletions(-)
(quoted diff) +0 -0

b/Documentation/translations/it_IT/process/license-rules.rst index f058e06996dc..06abeb7dd307 100644

Documentation/translations/it_IT/process/license-rules.rst essere categorizzate in: · line 306

Quoted 5 lines
Documentation/translations/it_IT/process/license-rules.rst +1 -1
@@ -303,7 +303,7 @@ essere categorizzate in:
      LICENSES/dual
 
    I file in questa cartella contengono il testo completo della rispettiva
-   licenza e i suoi `Metatags`_.  I nomi dei file sono identici agli
+   licenza e i suoi `Metatags`.  I nomi dei file sono identici agli

Remove 's' instead of '_' and then the link is correct

Metatag_

Quoted 33 lines
Documentation/translations/it_IT/process/license-rules.rst +0 -4
    identificatori di licenza SPDX che dovrebbero essere usati nei file
    sorgenti.
 
@@ -326,19 +326,19 @@ essere categorizzate in:
 
    Esempio del formato del file::
 
-   Valid-License-Identifier: MPL-1.1
-   SPDX-URL: https://spdx.org/licenses/MPL-1.1.html
-   Usage-Guide:
-     Do NOT use. The MPL-1.1 is not GPL2 compatible. It may only be used

for - dual-licensed files where the other license is GPL2 compatible. -
If you end up using this it MUST be used together with a GPL2
compatible - license using "OR".

Documentation/translations/it_IT/process/license-rules.rst +4 -6
-     To use the Mozilla Public License version 1.1 put the following SPDX
-     tag/value pair into a comment according to the placement guidelines in
-     the licensing rules documentation:
-   SPDX-License-Identifier: MPL-1.1
-   License-Text:
-     Full license text
+    Valid-License-Identifier: MPL-1.1
+    SPDX-URL: https://spdx.org/licenses/MPL-1.1.html
+    Usage-Guide:
+      Do NOT use. The MPL-1.1 is not GPL2 compatible. It may only be used

for + dual-licensed files where the other license is GPL2 compatible.
+ If you end up using this it MUST be used together with a GPL2
compatible + license using "OR".

Documentation/translations/it_IT/process/license-rules.rst +2 -0
+      To use the Mozilla Public License version 1.1 put the following SPDX
+      tag/value pair into a comment according to the placement guidelines

in + the licensing rules documentation:

Documentation/translations/it_IT/process/license-rules.rst +3 -0
+    SPDX-License-Identifier: MPL-1.1
+    License-Text:
+      Full license text
#32 lore raw

PATCH 16/22 docs: gpio: driver.rst: fix a bad tag

In reply to Mauro Carvalho Chehab

With ReST, [foo]_ means a reference to foo, causing this warning:

Documentation/driver-api/gpio/driver.rst:419: WARNING: Unknown target name: "devm".

Fix it by using a literal for the name.

---
 Documentation/driver-api/gpio/driver.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/driver-api/gpio/driver.rst +1 -1
index 1ce7fcd0f989..25e2ddeb4f31 100644
@@ -418,7 +418,7 @@ symbol:
 
 If there is a need to exclude certain GPIO lines from the IRQ domain handled by
 these helpers, we can set .irq.need_valid_mask of the gpiochip before
-[devm_]gpiochip_add_data() is called. This allocates an .irq.valid_mask with as
+``[devm_]gpiochip_add_data()`` is called. This allocates an .irq.valid_mask with as
 many bits set as there are GPIO lines in the chip, each bit representing line
 0..n-1. Drivers can exclude GPIO lines by clearing bits from this mask. The mask
 must be filled in before gpiochip_irqchip_add() or gpiochip_irqchip_add_nested()
Signature · 1 line
2.21.0
#33 lore raw

Re: [PATCH 16/22] docs: gpio: driver.rst: fix a bad tag

Quoted 7 lines · Mauro Carvalho Chehab

With ReST, [foo]_ means a reference to foo, causing this warning:

Documentation/driver-api/gpio/driver.rst:419: WARNING: Unknown target name: "devm".

Fix it by using a literal for the name.

Patch applied to the GPIO tree.

Yours,
Linus Walleij

#34 lore raw

PATCH 17/22 docs: soundwire: locking: fix tags for a code-block

In reply to Mauro Carvalho Chehab

There's an ascii artwork at Example 1 whose code-block is not properly idented, causing those warnings.

Documentation/driver-api/soundwire/locking.rst:50: WARNING: Inconsistent literal block quoting. Documentation/driver-api/soundwire/locking.rst:51: WARNING: Line block ends without a blank line. Documentation/driver-api/soundwire/locking.rst:55: WARNING: Inline substitution_reference start-string without end-string. Documentation/driver-api/soundwire/locking.rst:56: WARNING: Line block ends without a blank line.

---
 Documentation/driver-api/soundwire/locking.rst | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)
Documentation/driver-api/soundwire/locking.rst +3 -1
index 253f73555255..3a7ffb3d87f3 100644
@@ -44,7 +44,9 @@ Message transfer.
      b. Transfer message (Read/Write) to Slave1 or broadcast message on
         Bus in case of bank switch.
 
-     c. Release Message lock ::
+     c. Release Message lock
+
+     ::
 
 	+----------+                    +---------+
 	|          |                    |         |
Signature · 1 line
2.21.0
#35 lore raw

PATCH 18/22 docs: security: trusted-encrypted.rst: fix code-block tag

In reply to Mauro Carvalho Chehab

The code-block tag is at the wrong place, causing those warnings:

Documentation/security/keys/trusted-encrypted.rst:112: WARNING: Literal block expected; none found. Documentation/security/keys/trusted-encrypted.rst:121: WARNING: Unexpected indentation. Documentation/security/keys/trusted-encrypted.rst:122: WARNING: Block quote ends without a blank line; unexpected unindent. Documentation/security/keys/trusted-encrypted.rst:123: WARNING: Block quote ends without a blank line; unexpected unindent.

---
 Documentation/security/keys/trusted-encrypted.rst | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)
Documentation/security/keys/trusted-encrypted.rst +3 -1
index 7b35fcb58933..50ac8bcd6970 100644
@@ -107,12 +107,14 @@ Where::
 
 Examples of trusted and encrypted key usage:
 
-Create and save a trusted key named "kmk" of length 32 bytes::
+Create and save a trusted key named "kmk" of length 32 bytes.
 
 Note: When using a TPM 2.0 with a persistent key with handle 0x81000001,
 append 'keyhandle=0x81000001' to statements between quotes, such as
 "new 32 keyhandle=0x81000001".
 
+::
+
     $ keyctl add trusted kmk "new 32" @u
     440502848
 
Signature · 1 line
2.21.0
maintainer Acked-by on v1 18/22
#36 lore raw

Re: [PATCH 18/22] docs: security: trusted-encrypted.rst: fix code-block tag

Quoted 9 lines · Mauro Carvalho Chehab

The code-block tag is at the wrong place, causing those warnings:

Documentation/security/keys/trusted-encrypted.rst:112: WARNING: Literal block expected; none found. Documentation/security/keys/trusted-encrypted.rst:121: WARNING: Unexpected indentation. Documentation/security/keys/trusted-encrypted.rst:122: WARNING: Block quote ends without a blank line; unexpected unindent. Documentation/security/keys/trusted-encrypted.rst:123: WARNING: Block quote ends without a blank line; unexpected unindent.

Signature · 2 lines
James Morris
<[email protected]>
Acked-by on v1 18/22
#37 lore raw

Re: [PATCH 18/22] docs: security: trusted-encrypted.rst: fix code-block tag

In reply to Mauro Carvalho Chehab
Quoted 9 lines · Mauro Carvalho Chehab

The code-block tag is at the wrong place, causing those warnings:

Documentation/security/keys/trusted-encrypted.rst:112: WARNING: Literal block expected; none found. Documentation/security/keys/trusted-encrypted.rst:121: WARNING: Unexpected indentation. Documentation/security/keys/trusted-encrypted.rst:122: WARNING: Block quote ends without a blank line; unexpected unindent. Documentation/security/keys/trusted-encrypted.rst:123: WARNING: Block quote ends without a blank line; unexpected unindent.

/Jarkko

#38 lore raw

PATCH 19/22 docs: security: core.rst: Fix several warnings

In reply to Mauro Carvalho Chehab

Multi-line literal markups only work when they're idented at the same level, with is not the case here:

Documentation/security/keys/core.rst:1597: WARNING: Inline literal start-string without end-string. Documentation/security/keys/core.rst:1597: WARNING: Inline emphasis start-string without end-string. Documentation/security/keys/core.rst:1597: WARNING: Inline emphasis start-string without end-string. Documentation/security/keys/core.rst:1598: WARNING: Inline emphasis start-string without end-string. Documentation/security/keys/core.rst:1598: WARNING: Inline emphasis start-string without end-string. Documentation/security/keys/core.rst:1600: WARNING: Inline literal start-string without end-string. Documentation/security/keys/core.rst:1600: WARNING: Inline emphasis start-string without end-string. Documentation/security/keys/core.rst:1600: WARNING: Inline emphasis start-string without end-string. Documentation/security/keys/core.rst:1600: WARNING: Inline emphasis start-string without end-string. Documentation/security/keys/core.rst:1600: WARNING: Inline emphasis start-string without end-string. Documentation/security/keys/core.rst:1666: WARNING: Inline literal start-string without end-string. Documentation/security/keys/core.rst:1666: WARNING: Inline emphasis start-string without end-string. Documentation/security/keys/core.rst:1666: WARNING: Inline emphasis start-string without end-string. Documentation/security/keys/core.rst:1666: WARNING: Inline emphasis start-string without end-string.

Fix it by using a code-block instead.

---
 Documentation/security/keys/core.rst | 16 ++++++++++------
 1 file changed, 10 insertions(+), 6 deletions(-)
Documentation/security/keys/core.rst +10 -6
index 9521c4207f01..3fd60dcb2dc6 100644
@@ -1594,10 +1594,12 @@ The structure has a number of fields, some of which are mandatory:
      attempted key link operation. If there is no match, -EINVAL is returned.
 
 
-  *  ``int (*asym_eds_op)(struct kernel_pkey_params *params,
-			  const void *in, void *out);``
-     ``int (*asym_verify_signature)(struct kernel_pkey_params *params,
-				    const void *in, const void *in2);``
+  *  ``asym_eds_op`` and ``asym_verify_signature``::
+
+       int (*asym_eds_op)(struct kernel_pkey_params *params,
+			  const void *in, void *out);
+       int (*asym_verify_signature)(struct kernel_pkey_params *params,
+				    const void *in, const void *in2);
 
      These methods are optional.  If provided the first allows a key to be
      used to encrypt, decrypt or sign a blob of data, and the second allows a
@@ -1662,8 +1664,10 @@ The structure has a number of fields, some of which are mandatory:
      required crypto isn't available.
 
 
-  *  ``int (*asym_query)(const struct kernel_pkey_params *params,
-			 struct kernel_pkey_query *info);``
+  *  ``asym_query``::
+
+       int (*asym_query)(const struct kernel_pkey_params *params,
+			 struct kernel_pkey_query *info);
 
      This method is optional.  If provided it allows information about the
      public or asymmetric key held in the key to be determined.
Signature · 1 line
2.21.0
#39 lore raw

PATCH 20/22 docs: net: dpio-driver.rst: fix two codeblock warnings

In reply to Mauro Carvalho Chehab

Documentation/networking/device_drivers/freescale/dpaa2/dpio-driver.rst:43: WARNING: Definition list ends without a blank line; unexpected unindent. Documentation/networking/device_drivers/freescale/dpaa2/dpio-driver.rst:63: WARNING: Unexpected indentation. looking for now-outdated files... none found

---
 .../networking/device_drivers/freescale/dpaa2/dpio-driver.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
Documentation/networking/device_drivers/freescale/dpaa2/dpio-driver.rst +2 -2
index 5045df990a4c..17dbee1ac53e 100644
@@ -39,8 +39,7 @@ The Linux DPIO driver consists of 3 primary components--
 
    DPIO service-- provides APIs to other Linux drivers for services
 
-   QBman portal interface-- sends portal commands, gets responses
-::
+   QBman portal interface-- sends portal commands, gets responses::
 
           fsl-mc          other
            bus           drivers
@@ -60,6 +59,7 @@ The Linux DPIO driver consists of 3 primary components--
 
 The diagram below shows how the DPIO driver components fit with the other
 DPAA2 Linux driver components::
+
                                                    +------------+
                                                    | OS Network |
                                                    |   Stack    |
Signature · 1 line
2.21.0
#40 lore raw

PATCH 21/22 docs: net: sja1105.rst: fix table format

In reply to Mauro Carvalho Chehab

There's a table there with produces two warnings when built with Sphinx:

Documentation/networking/dsa/sja1105.rst:91: WARNING: Block quote ends without a blank line; unexpected unindent. Documentation/networking/dsa/sja1105.rst:91: WARNING: Block quote ends without a blank line; unexpected unindent.

It will still produce a table, but the html output is wrong, as it won't interpret the second line as the continuation for the first ones, because identation doesn't match.

After the change, the output looks a way better and we got rid of two warnings.

---
 Documentation/networking/dsa/sja1105.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
Documentation/networking/dsa/sja1105.rst +3 -3
index ea7bac438cfd..cb2858dece93 100644
@@ -86,13 +86,13 @@ functionality.
 The following traffic modes are supported over the switch netdevices:
 
 +--------------------+------------+------------------+------------------+
-|                    | Standalone |   Bridged with   |   Bridged with   |
-|                    |    ports   | vlan_filtering 0 | vlan_filtering 1 |
+|                    | Standalone | Bridged with     | Bridged with     |
+|                    | ports      | vlan_filtering 0 | vlan_filtering 1 |
 +====================+============+==================+==================+
 | Regular traffic    |     Yes    |       Yes        |  No (use master) |
 +--------------------+------------+------------------+------------------+
 | Management traffic |     Yes    |       Yes        |       Yes        |
-|    (BPDU, PTP)     |            |                  |                  |
+| (BPDU, PTP)        |            |                  |                  |
 +--------------------+------------+------------------+------------------+
 
 Switching features
Signature · 1 line
2.21.0
Acked-by on v1 21/22
#41 lore raw

Re: [PATCH 21/22] docs: net: sja1105.rst: fix table format

Quoted 41 lines · Mauro Carvalho Chehab

There's a table there with produces two warnings when built with Sphinx:

Documentation/networking/dsa/sja1105.rst:91: WARNING: Block quote ends without a blank line; unexpected unindent. Documentation/networking/dsa/sja1105.rst:91: WARNING: Block quote ends without a blank line; unexpected unindent.

It will still produce a table, but the html output is wrong, as it won't interpret the second line as the continuation for the first ones, because identation doesn't match.

After the change, the output looks a way better and we got rid of two warnings.

---
 Documentation/networking/dsa/sja1105.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
Documentation/networking/dsa/sja1105.rst +3 -4
index ea7bac438cfd..cb2858dece93 100644
@@ -86,13 +86,13 @@ functionality.
 The following traffic modes are supported over the switch netdevices:
 
 +--------------------+------------+------------------+------------------+
-|                    | Standalone |   Bridged with   |   Bridged with   |
-|                    |    ports   | vlan_filtering 0 | vlan_filtering 1 |
+|                    | Standalone | Bridged with     | Bridged with     |
+|                    | ports      | vlan_filtering 0 | vlan_filtering 1 |
 +====================+============+==================+==================+
 | Regular traffic    |     Yes    |       Yes        |  No (use master) |
 +--------------------+------------+------------------+------------------+
 | Management traffic |     Yes    |       Yes        |       Yes        |
-|    (BPDU, PTP)     |            |                  |                  |
+| (BPDU, PTP)        |            |                  |                  |
 +--------------------+------------+------------------+------------------+
 
 Switching features
--
Quoted 2 lines

2.21.0

#42 lore raw

PATCH 22/22 docs: fix broken documentation links

In reply to Mauro Carvalho Chehab

Mostly 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/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 +-
 48 files changed, 77 insertions(+), 78 deletions(-)
Documentation/acpi/dsd/leds.txt +1 -1
index 81a63af42ed2..cc58b1a574c5 100644
@@ -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
index 0124980dca2d..8d3273e32eb1 100644
@@ -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
index 138f6664b2e2..4a02d1346635 100644
@@ -53,7 +53,7 @@
 			ACPI_DEBUG_PRINT statements, e.g.,
 			    ACPI_DEBUG_PRINT((ACPI_DB_INFO, ...
 			The debug_level mask defaults to "info".  See
-			Documentation/acpi/debug.txt for more information about
+			Documentation/firmware-guide/acpi/debug.rst for more information about
 			debug layers and levels.
 
 			Enable processor driver info messages:
@@ -963,7 +963,7 @@
 			for details.
 
 	nompx		[X86] Disables Intel Memory Protection Extensions.
-			See Documentation/x86/intel_mpx.txt for more
+			See Documentation/x86/intel_mpx.rst for more
 			information about the feature.
 
 	nopku		[X86] Disable Memory Protection Keys CPU feature found
@@ -1189,7 +1189,7 @@
 			that is to be dynamically loaded by Linux. If there are
 			multiple variables with the same name but with different
 			vendor GUIDs, all of them will be loaded. See
-			Documentation/acpi/ssdt-overlays.txt for details.
+			Documentation/admin-guide/acpi/ssdt-overlays.rst for details.
 
 
 	eisa_irq_edge=	[PARISC,HW]
@@ -2383,7 +2383,7 @@
 
 	mce		[X86-32] Machine Check Exception
 
-	mce=option	[X86-64] See Documentation/x86/x86_64/boot-options.txt
+	mce=option	[X86-64] See Documentation/x86/x86_64/boot-options.rst
 
 	md=		[HW] RAID subsystems devices and level
 			See Documentation/admin-guide/md.rst.
@@ -2439,7 +2439,7 @@
 			set according to the
 			CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE kernel config
 			option.
-			See Documentation/memory-hotplug.txt.
+			See Documentation/admin-guide/mm/memory-hotplug.rst.
 
 	memmap=exactmap	[KNL,X86] Enable setting of an exact
 			E820 memory map, as specified by the user.
@@ -2528,7 +2528,7 @@
 			mem_encrypt=on:		Activate SME
 			mem_encrypt=off:	Do not activate SME
 
-			Refer to Documentation/x86/amd-memory-encryption.txt
+			Refer to Documentation/virtual/kvm/amd-memory-encryption.rst
 			for details on when memory encryption can be activated.
 
 	mem_sleep_default=	[SUSPEND] Default system suspend mode:
@@ -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
index c7495e42e6f4..2b20f5f7380d 100644
@@ -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
index c812e25ae90f..25fc687419db 100644
@@ -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
index 12b18f82d441..efa2c8b9b85a 100644
@@ -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
index 7ef2dbe48e8a..14d2eee96b3d 100644
@@ -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
index e86bd2f64117..60f8640f2b2f 100644
@@ -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
index b37f3f7b8926..ce91518bf9f4 100644
@@ -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
index 5e4d8aa68913..fdecb6d711db 100644
@@ -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
index 850be9696931..1252617b520f 100644
@@ -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
index d0b077b73f5f..0aa7e2c5d32a 100644
@@ -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
index 0d85ac1935b7..5a3e2f331e8c 100644
@@ -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
index f0c86fbb3b48..92f7f34b021a 100644
@@ -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/howto.rst +1 -1
index 9903ac7c566b..44e6077730e8 100644
@@ -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
index 48e88e5ad2c5..4f206cee31a7 100644
@@ -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
index 5301e9d55255..8bb777941394 100644
@@ -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
index ab88a4514163..44856417e6a5 100644
@@ -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
index 2f69836b8445..6a4285a3c7a4 100644
@@ -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
index 74fbb78b3c67..04df57b9aa3f 100644
@@ -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
index 5cfbea4ce575..a38d7273705a 100644
@@ -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
index 8869742a85df..0f220264cc23 100644
@@ -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
index 07bf740bea91..31cc2f423aa8 100644
@@ -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
index 8c1c636308c8..e868d2bd48b8 100644
@@ -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
index 2bbbd4d1ba31..78fdf2dd71d1 100644
@@ -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
index f730680dc818..59f598543203 100644
@@ -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
index 850b8762e889..90d791ca1a95 100644
@@ -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
index 11aa3b2afa4d..33f9fc38d014 100644
@@ -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
index f6f6ef436599..101eb944f13c 100644
@@ -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
index 793c14c372cb..288b065955b7 100644
@@ -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
index 88bca456da99..52e5f5f2240d 100644
@@ -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
index e1f3ba19ba54..06d4e67f31ab 100644
@@ -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
index 22f60dd26460..b07e7069b09e 100644
@@ -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
index dcd272dbd0a9..f62b498b18fb 100644
@@ -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
index 7f61431c75fb..400c1ba033aa 100644
@@ -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
index 1861a2ba0f2b..c0a502f7e3a7 100644
@@ -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
index 283ee94224c6..2438f37f2ca1 100644
@@ -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
index b17b79e612a3..ac6280ad43a1 100644
@@ -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
index 56af3f650fa3..89fb8e14676f 100644
@@ -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
index 1e3ed41ae1f3..69938dbae2d0 100644
@@ -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
index de1804aeaf69..98e3db7a89cd 100644
@@ -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
index 1f966670c8dc..623eb58560b9 100644
@@ -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
index 47f58cfb6a19..df1318d85f7d 100644
@@ -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
index ee8d1f311858..6e5fb81bde4b 100644
@@ -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
index aeac3676dd4d..6d75ed71970c 100644
@@ -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
index 2f5a12b88a86..25f2bb3a991d 100644
@@ -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
index 4dd11a554b9b..de094670050b 100644
@@ -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
index 5d546dcdbc80..798a5ddeee55 100644
@@ -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
Reviewed-by on v1 22/22
#43 lore raw

Re: [PATCH 22/22] 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.

Didn't I ack this already?

For the I2C part:

_______________________________________________
Virtualization mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

maintainer
#45 lore raw

Re: [PATCH 22/22] docs: fix broken documentation links

In reply to Mauro Carvalho Chehab
Quoted 2 lines · CEST Mauro Carvalho Chehab

Mostly due to x86 and acpi conversion, several documentation links are still pointing to the old file. Fix them.

For the Italian documentation I just send I patch to fix them in a dedicated patch

Quoted 70 lines
---
 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/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 +-
 48 files changed, 77 insertions(+), 78 deletions(-)
(quoted diff) +0 -0

b/Documentation/acpi/dsd/leds.txt index 81a63af42ed2..cc58b1a574c5 100644

Documentation/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.rst index 0124980dca2d..8d3273e32eb1 100644

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 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

Documentation/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.txt index 138f6664b2e2..4a02d1346635 100644

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 -0
 			debug 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 -0
 			information 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 -0
 			multiple 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 -0
 			vendor 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 -1
 	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

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 -0
 	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

Documentation/admin-guide/kernel-parameters.txt

Quoted 3 lines
Documentation/admin-guide/kernel-parameters.txt +1 -1
 			option.
-			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 -0
 	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

Documentation/admin-guide/kernel-parameters.txt

Quoted 3 lines
Documentation/admin-guide/kernel-parameters.txt +0 -1
 			mem_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/virtual/kvm/amd-

memory-encryption.rst

Documentation/admin-guide/kernel-parameters.txt line 2532

Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +0 -0
 			for 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 -1
 	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.

Documentation/admin-guide/kernel-parameters.txt line 5055

Quoted 2 lines
Documentation/admin-guide/kernel-parameters.txt +0 -0
 	vga=		[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.rst index c7495e42e6f4..2b20f5f7380d 100644

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
 *************************************
(quoted diff) +0 -0

b/Documentation/devicetree/bindings/net/fsl-enetc.txt index c812e25ae90f..25fc687419db 100644

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:
 
(quoted diff) +0 -0

b/Documentation/devicetree/bindings/pci/amlogic,meson-pcie.txt index 12b18f82d441..efa2c8b9b85a 100644

Documentation/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 PCI

core. 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.txt b/Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txt index 7ef2dbe48e8a..14d2eee96b3d 100644

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 264 lines
Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txt +1 -1
 		    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 diff --git a/Documentation/devicetree/booting-without-of.txt b/Documentation/devicetree/booting-without-of.txt index e86bd2f64117..60f8640f2b2f 100644

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
(quoted diff) +0 -0

b/Documentation/driver-api/gpio/board.rst index b37f3f7b8926..ce91518bf9f4 100644

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
 -------------
(quoted diff) +0 -0

b/Documentation/driver-api/gpio/consumer.rst index 5e4d8aa68913..fdecb6d711db 100644

Documentation/driver-api/gpio/consumer.rst +0 -0
@@ -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.

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.rst index 850be9696931..1252617b520f 100644

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

(quoted diff) +0 -0

b/Documentation/firmware-guide/acpi/method-tracing.rst index d0b077b73f5f..0aa7e2c5d32a 100644

Documentation/firmware-guide/acpi/method-tracing.rst +0 -0
@@ -68,7 +68,7 @@ c. Filter out the debug layer/level matched logs when the

specified

Where:

    0xXXXXXXXX/0xYYYYYYYY
Documentation/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 possible

debug 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 -0

b/Documentation/i2c/instantiating-devices index 0d85ac1935b7..5a3e2f331e8c 100644

Documentation/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. +which

is currently located at Documentation/firmware-guide/acpi/enumeration.rst.

Method 2: Instantiate the devices explicitly

(quoted diff) +0 -0

b/Documentation/sysctl/kernel.txt index f0c86fbb3b48..92f7f34b021a 100644

Documentation/sysctl/kernel.txt +0 -0
@@ -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/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 example

above, this file will contain the value 564 = 0x234.

See the type_of_loader and ext_loader_ver fields in

Documentation/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/howto.rst index 9903ac7c566b..44e6077730e8 100644

Documentation/translations/it_IT/process/howto.rst +0 -0
@@ -131,7 +131,7 @@ Di seguito una lista di file che sono presenti nei

sorgente del kernel e che "Linux kernel patch submission format"

Documentation/translations/it_IT/process/howto.rst +0 -1
 		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: diff --git a/Documentation/translations/it_IT/process/stable-kernel-rules.rst b/Documentation/translations/it_IT/process/stable-kernel-rules.rst index 48e88e5ad2c5..4f206cee31a7 100644

Documentation/translations/it_IT/process/stable-kernel-rules.rst +0 -0
@@ -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

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:

https://patchwork.ozlabs.org/bundle/davem/stable/?series=&submitter=&state=
*&q=&archive= diff --git a/Documentation/translations/zh_CN/process/4.Coding.rst b/Documentation/translations/zh_CN/process/4.Coding.rst index 5301e9d55255..8bb777941394 100644

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>` 描述了内核的所有引导时间参数。任何添加新参数的补丁都应该向该文件添加适当的

(quoted diff) +0 -0

b/Documentation/x86/x86_64/5level-paging.rst index ab88a4514163..44856417e6a5 100644

Documentation/x86/x86_64/5level-paging.rst +0 -0
@@ -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/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.rst index
2f69836b8445..6a4285a3c7a4 100644

Documentation/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 runtime

tunables. +Please see Documentation/x86/x86_64/machinecheck.rst for sysfs runtime tunables.

mce=off

Documentation/x86/x86_64/boot-options.rst +1 -1
 		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
(quoted diff) +0 -0

b/Documentation/x86/x86_64/fake-numa-for-cpusets.rst index 74fbb78b3c67..04df57b9aa3f 100644

Documentation/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, 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 diff --git a/MAINTAINERS b/MAINTAINERS
index 5cfbea4ce575..a38d7273705a 100644

MAINTAINERS +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.txt

MAINTAINERS +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
index 8869742a85df..0f220264cc23 100644

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.c index 07bf740bea91..31cc2f423aa8 100644

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

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
index 8c1c636308c8..e868d2bd48b8 100644
@@ -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 -1
 	  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 +0 -0
index 2bbbd4d1ba31..78fdf2dd71d1 100644
@@ -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 -1
 	  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

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 is

described - 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 enable
CONFIG_BLK_DEV_INITRD in 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 -0
 	  should'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 more

information. 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 -2
 	  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.
 

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 -1
 	  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
index f730680dc818..59f598543203 100644
@@ -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 +0 -0
index 850b8762e889..90d791ca1a95 100644
@@ -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 loadflags
arch/x86/entry/entry_64.S +1 -1
index 11aa3b2afa4d..33f9fc38d014 100644
@@ -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.h index f6f6ef436599..101eb944f13c 100644

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.
(quoted diff) +0 -0

b/arch/x86/include/asm/page_64_types.h index 793c14c372cb..288b065955b7 100644

arch/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 memory

map. */

#define __PHYSICAL_MASK_SHIFT 52

(quoted diff) +0 -0

b/arch/x86/include/asm/pgtable_64_types.h index 88bca456da99..52e5f5f2240d 100644

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

(quoted diff) +0 -0

b/arch/x86/kernel/cpu/microcode/amd.c index e1f3ba19ba54..06d4e67f31ab 100644

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";
(quoted diff) +0 -0

b/arch/x86/kernel/kexec-bzimage64.c index 22f60dd26460..b07e7069b09e 100644

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
index dcd272dbd0a9..f62b498b18fb 100644
@@ -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
index 7f61431c75fb..400c1ba033aa 100644
@@ -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.c index 1861a2ba0f2b..c0a502f7e3a7 100644

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
index 283ee94224c6..2438f37f2ca1 100644
@@ -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 -0
 	  via 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 -1
 	  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

drivers/acpi/Kconfig config ACPI_TABLE_OVERRIDE_VIA_BUILTIN_INITRD · line 365

Quoted 5 lines
drivers/acpi/Kconfig +0 -0
 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

drivers/acpi/Kconfig config ACPI_TABLE_OVERRIDE_VIA_BUILTIN_INITRD

Quoted 4 lines
drivers/acpi/Kconfig +1 -1
 	  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

drivers/acpi/Kconfig config ACPI_DEBUG · line 376

Quoted 7 lines
drivers/acpi/Kconfig +0 -0
 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

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.rst to 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 -1
 	  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

drivers/acpi/Kconfig config ACPI_CUSTOM_METHOD · line 451

Quoted 1 line
drivers/acpi/Kconfig +0 -0
 	  kernel 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.c index b17b79e612a3..ac6280ad43a1 100644

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);
 
(quoted diff) +0 -0

b/drivers/staging/fieldbus/Documentation/fieldbus_dev.txt index 56af3f650fa3..89fb8e14676f 100644

drivers/staging/fieldbus/Documentation/fieldbus_dev.txt +0 -0
@@ -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:

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 get

their diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c index 1e3ed41ae1f3..69938dbae2d0 100644

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
index de1804aeaf69..98e3db7a89cd 100644
@@ -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 +0 -0
index 1f966670c8dc..623eb58560b9 100644
@@ -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 {

include/linux/fs_context.h +0 -0
 	const struct fs_context_operations *ops;
include/linux/lsm_hooks.h +0 -0
index 47f58cfb6a19..df1318d85f7d 100644

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
index ee8d1f311858..6e5fb81bde4b 100644
@@ -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 -0
 	  determines what happens to newly added memory regions. Policy 

setting

Quoted 6 lines
mm/Kconfig +1 -1
 	  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

Quoted 64 lines
mm/Kconfig +0 -0
 	  'online' state by default.
security/Kconfig +1 -1
index aeac3676dd4d..6d75ed71970c 100644
@@ -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
index 2f5a12b88a86..25f2bb3a991d 100644
@@ -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.txt index 4dd11a554b9b..de094670050b 100644

tools/objtool/Documentation/stack-validation.txt +0 -0
@@ -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

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.c index 5d546dcdbc80..798a5ddeee55 100644

tools/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 (see Documentation/x86/protection-keys.rst) *
* There are examples in here of:
* * how to set protection keys on memory

maintainer Acked-by
#46 lore raw

Re: [PATCH 22/22] docs: fix broken documentation links

Quoted 6 lines · Federico Vaga
Quoted 2 lines · CEST Mauro Carvalho Chehab

Mostly due to x86 and acpi conversion, several documentation links are still pointing to the old file. Fix them.

For the Italian documentation I just send I patch to fix them in a dedicated patch

for the vhost change.

Quoted 1,021 lines
Quoted 70 lines
---
 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/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 +-
 48 files changed, 77 insertions(+), 78 deletions(-)
(quoted diff) +0 -0

b/Documentation/acpi/dsd/leds.txt index 81a63af42ed2..cc58b1a574c5 100644

Documentation/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.rst index 0124980dca2d..8d3273e32eb1 100644

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 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

Documentation/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.txt index 138f6664b2e2..4a02d1346635 100644

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 -0
 			debug 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 -0
 			information 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 -0
 			multiple 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 -0
 			vendor 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 -1
 	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

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 -0
 	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

Documentation/admin-guide/kernel-parameters.txt

Quoted 3 lines
Documentation/admin-guide/kernel-parameters.txt +1 -1
 			option.
-			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 -0
 	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

Documentation/admin-guide/kernel-parameters.txt

Quoted 3 lines
Documentation/admin-guide/kernel-parameters.txt +0 -1
 			mem_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/virtual/kvm/amd-

memory-encryption.rst

Documentation/admin-guide/kernel-parameters.txt line 2532

Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +0 -0
 			for 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 -1
 	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.

Documentation/admin-guide/kernel-parameters.txt line 5055

Quoted 2 lines
Documentation/admin-guide/kernel-parameters.txt +0 -0
 	vga=		[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.rst index c7495e42e6f4..2b20f5f7380d 100644

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
 *************************************
(quoted diff) +0 -0

b/Documentation/devicetree/bindings/net/fsl-enetc.txt index c812e25ae90f..25fc687419db 100644

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:
 
(quoted diff) +0 -0

b/Documentation/devicetree/bindings/pci/amlogic,meson-pcie.txt index 12b18f82d441..efa2c8b9b85a 100644

Documentation/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 PCI

core. 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.txt b/Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txt index 7ef2dbe48e8a..14d2eee96b3d 100644

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 264 lines
Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txt +1 -1
 		    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 diff --git a/Documentation/devicetree/booting-without-of.txt b/Documentation/devicetree/booting-without-of.txt index e86bd2f64117..60f8640f2b2f 100644

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
(quoted diff) +0 -0

b/Documentation/driver-api/gpio/board.rst index b37f3f7b8926..ce91518bf9f4 100644

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
 -------------
(quoted diff) +0 -0

b/Documentation/driver-api/gpio/consumer.rst index 5e4d8aa68913..fdecb6d711db 100644

Documentation/driver-api/gpio/consumer.rst +0 -0
@@ -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.

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.rst index 850be9696931..1252617b520f 100644

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

(quoted diff) +0 -0

b/Documentation/firmware-guide/acpi/method-tracing.rst index d0b077b73f5f..0aa7e2c5d32a 100644

Documentation/firmware-guide/acpi/method-tracing.rst +0 -0
@@ -68,7 +68,7 @@ c. Filter out the debug layer/level matched logs when the

specified

Where:

    0xXXXXXXXX/0xYYYYYYYY
Documentation/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 possible

debug 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 -0

b/Documentation/i2c/instantiating-devices index 0d85ac1935b7..5a3e2f331e8c 100644

Documentation/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. +which

is currently located at Documentation/firmware-guide/acpi/enumeration.rst.

Method 2: Instantiate the devices explicitly

(quoted diff) +0 -0

b/Documentation/sysctl/kernel.txt index f0c86fbb3b48..92f7f34b021a 100644

Documentation/sysctl/kernel.txt +0 -0
@@ -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/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 example

above, this file will contain the value 564 = 0x234.

See the type_of_loader and ext_loader_ver fields in

Documentation/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/howto.rst index 9903ac7c566b..44e6077730e8 100644

Documentation/translations/it_IT/process/howto.rst +0 -0
@@ -131,7 +131,7 @@ Di seguito una lista di file che sono presenti nei

sorgente del kernel e che "Linux kernel patch submission format"

Documentation/translations/it_IT/process/howto.rst +0 -1
 		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: diff --git a/Documentation/translations/it_IT/process/stable-kernel-rules.rst b/Documentation/translations/it_IT/process/stable-kernel-rules.rst index 48e88e5ad2c5..4f206cee31a7 100644

Documentation/translations/it_IT/process/stable-kernel-rules.rst +0 -0
@@ -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

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:

https://patchwork.ozlabs.org/bundle/davem/stable/?series=&submitter=&state=
*&q=&archive= diff --git a/Documentation/translations/zh_CN/process/4.Coding.rst b/Documentation/translations/zh_CN/process/4.Coding.rst index 5301e9d55255..8bb777941394 100644

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>` 描述了内核的所有引导时间参数。任何添加新参数的补丁都应该向该文件添加适当的

(quoted diff) +0 -0

b/Documentation/x86/x86_64/5level-paging.rst index ab88a4514163..44856417e6a5 100644

Documentation/x86/x86_64/5level-paging.rst +0 -0
@@ -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/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.rst index
2f69836b8445..6a4285a3c7a4 100644

Documentation/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 runtime

tunables. +Please see Documentation/x86/x86_64/machinecheck.rst for sysfs runtime tunables.

mce=off

Documentation/x86/x86_64/boot-options.rst +1 -1
 		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
(quoted diff) +0 -0

b/Documentation/x86/x86_64/fake-numa-for-cpusets.rst index 74fbb78b3c67..04df57b9aa3f 100644

Documentation/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, 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 diff --git a/MAINTAINERS b/MAINTAINERS
index 5cfbea4ce575..a38d7273705a 100644

MAINTAINERS +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.txt

MAINTAINERS +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
index 8869742a85df..0f220264cc23 100644

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.c index 07bf740bea91..31cc2f423aa8 100644

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

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
index 8c1c636308c8..e868d2bd48b8 100644
@@ -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 -1
 	  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 +0 -0
index 2bbbd4d1ba31..78fdf2dd71d1 100644
@@ -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 -1
 	  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

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 is

described - 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 enable
CONFIG_BLK_DEV_INITRD in 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 -0
 	  should'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 more

information. 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 -2
 	  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.
 

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 -1
 	  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
index f730680dc818..59f598543203 100644
@@ -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 +0 -0
index 850b8762e889..90d791ca1a95 100644
@@ -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 loadflags
arch/x86/entry/entry_64.S +1 -1
index 11aa3b2afa4d..33f9fc38d014 100644
@@ -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.h index f6f6ef436599..101eb944f13c 100644

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.
(quoted diff) +0 -0

b/arch/x86/include/asm/page_64_types.h index 793c14c372cb..288b065955b7 100644

arch/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 memory

map. */

#define __PHYSICAL_MASK_SHIFT 52

(quoted diff) +0 -0

b/arch/x86/include/asm/pgtable_64_types.h index 88bca456da99..52e5f5f2240d 100644

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

(quoted diff) +0 -0

b/arch/x86/kernel/cpu/microcode/amd.c index e1f3ba19ba54..06d4e67f31ab 100644

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";
(quoted diff) +0 -0

b/arch/x86/kernel/kexec-bzimage64.c index 22f60dd26460..b07e7069b09e 100644

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
index dcd272dbd0a9..f62b498b18fb 100644
@@ -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
index 7f61431c75fb..400c1ba033aa 100644
@@ -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.c index 1861a2ba0f2b..c0a502f7e3a7 100644

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
index 283ee94224c6..2438f37f2ca1 100644
@@ -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 -0
 	  via 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 -1
 	  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

drivers/acpi/Kconfig config ACPI_TABLE_OVERRIDE_VIA_BUILTIN_INITRD · line 365

Quoted 5 lines
drivers/acpi/Kconfig +0 -0
 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

drivers/acpi/Kconfig config ACPI_TABLE_OVERRIDE_VIA_BUILTIN_INITRD

Quoted 4 lines
drivers/acpi/Kconfig +1 -1
 	  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

drivers/acpi/Kconfig config ACPI_DEBUG · line 376

Quoted 7 lines
drivers/acpi/Kconfig +0 -0
 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

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.rst to 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 -1
 	  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

drivers/acpi/Kconfig config ACPI_CUSTOM_METHOD · line 451

Quoted 1 line
drivers/acpi/Kconfig +0 -0
 	  kernel 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.c index b17b79e612a3..ac6280ad43a1 100644

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);
 
(quoted diff) +0 -0

b/drivers/staging/fieldbus/Documentation/fieldbus_dev.txt index 56af3f650fa3..89fb8e14676f 100644

drivers/staging/fieldbus/Documentation/fieldbus_dev.txt +0 -0
@@ -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:

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 get

their diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c index 1e3ed41ae1f3..69938dbae2d0 100644

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
index de1804aeaf69..98e3db7a89cd 100644
@@ -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 +0 -0
index 1f966670c8dc..623eb58560b9 100644
@@ -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 {

include/linux/fs_context.h +0 -0
 	const struct fs_context_operations *ops;
include/linux/lsm_hooks.h +0 -0
index 47f58cfb6a19..df1318d85f7d 100644

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
index ee8d1f311858..6e5fb81bde4b 100644
@@ -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 -0
 	  determines what happens to newly added memory regions. Policy 

setting

Quoted 6 lines
mm/Kconfig +1 -1
 	  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

Quoted 64 lines
mm/Kconfig +0 -0
 	  'online' state by default.
security/Kconfig +1 -1
index aeac3676dd4d..6d75ed71970c 100644
@@ -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
index 2f5a12b88a86..25f2bb3a991d 100644
@@ -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.txt index 4dd11a554b9b..de094670050b 100644

tools/objtool/Documentation/stack-validation.txt +0 -0
@@ -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

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.c index 5d546dcdbc80..798a5ddeee55 100644

tools/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 (see Documentation/x86/protection-keys.rst) *
* There are examples in here of:
* * how to set protection keys on memory

maintainer Acked-by
#47 lore raw

Re: [PATCH 22/22] docs: fix broken documentation links

In reply to Federico Vaga
Quoted 6 lines · Federico Vaga
Quoted 2 lines · CEST Mauro Carvalho Chehab

Mostly due to x86 and acpi conversion, several documentation links are still pointing to the old file. Fix them.

For the Italian documentation I just send I patch to fix them in a dedicated patch

for the vhost change.

Quoted 1,005 lines
Quoted 70 lines
---
 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/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 +-
 48 files changed, 77 insertions(+), 78 deletions(-)
(quoted diff) +0 -0

b/Documentation/acpi/dsd/leds.txt index 81a63af42ed2..cc58b1a574c5 100644

Documentation/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.rst index 0124980dca2d..8d3273e32eb1 100644

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 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

Documentation/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.txt index 138f6664b2e2..4a02d1346635 100644

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 -0
 			debug 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 -0
 			information 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 -0
 			multiple 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 -0
 			vendor 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 -1
 	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

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 -0
 	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

Documentation/admin-guide/kernel-parameters.txt

Quoted 3 lines
Documentation/admin-guide/kernel-parameters.txt +1 -1
 			option.
-			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 -0
 	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

Documentation/admin-guide/kernel-parameters.txt

Quoted 3 lines
Documentation/admin-guide/kernel-parameters.txt +0 -1
 			mem_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/virtual/kvm/amd-

memory-encryption.rst

Documentation/admin-guide/kernel-parameters.txt line 2532

Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +0 -0
 			for 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 -1
 	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.

Documentation/admin-guide/kernel-parameters.txt line 5055

Quoted 2 lines
Documentation/admin-guide/kernel-parameters.txt +0 -0
 	vga=		[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.rst index c7495e42e6f4..2b20f5f7380d 100644

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
 *************************************
(quoted diff) +0 -0

b/Documentation/devicetree/bindings/net/fsl-enetc.txt index c812e25ae90f..25fc687419db 100644

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:
 
(quoted diff) +0 -0

b/Documentation/devicetree/bindings/pci/amlogic,meson-pcie.txt index 12b18f82d441..efa2c8b9b85a 100644

Documentation/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 PCI

core. 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.txt b/Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txt index 7ef2dbe48e8a..14d2eee96b3d 100644

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 264 lines
Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txt +1 -1
 		    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 diff --git a/Documentation/devicetree/booting-without-of.txt b/Documentation/devicetree/booting-without-of.txt index e86bd2f64117..60f8640f2b2f 100644

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
(quoted diff) +0 -0

b/Documentation/driver-api/gpio/board.rst index b37f3f7b8926..ce91518bf9f4 100644

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
 -------------
(quoted diff) +0 -0

b/Documentation/driver-api/gpio/consumer.rst index 5e4d8aa68913..fdecb6d711db 100644

Documentation/driver-api/gpio/consumer.rst +0 -0
@@ -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.

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.rst index 850be9696931..1252617b520f 100644

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

(quoted diff) +0 -0

b/Documentation/firmware-guide/acpi/method-tracing.rst index d0b077b73f5f..0aa7e2c5d32a 100644

Documentation/firmware-guide/acpi/method-tracing.rst +0 -0
@@ -68,7 +68,7 @@ c. Filter out the debug layer/level matched logs when the

specified

Where:

    0xXXXXXXXX/0xYYYYYYYY
Documentation/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 possible

debug 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 -0

b/Documentation/i2c/instantiating-devices index 0d85ac1935b7..5a3e2f331e8c 100644

Documentation/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. +which

is currently located at Documentation/firmware-guide/acpi/enumeration.rst.

Method 2: Instantiate the devices explicitly

(quoted diff) +0 -0

b/Documentation/sysctl/kernel.txt index f0c86fbb3b48..92f7f34b021a 100644

Documentation/sysctl/kernel.txt +0 -0
@@ -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/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 example

above, this file will contain the value 564 = 0x234.

See the type_of_loader and ext_loader_ver fields in

Documentation/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/howto.rst index 9903ac7c566b..44e6077730e8 100644

Documentation/translations/it_IT/process/howto.rst +0 -0
@@ -131,7 +131,7 @@ Di seguito una lista di file che sono presenti nei

sorgente del kernel e che "Linux kernel patch submission format"

Documentation/translations/it_IT/process/howto.rst +0 -1
 		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: diff --git a/Documentation/translations/it_IT/process/stable-kernel-rules.rst b/Documentation/translations/it_IT/process/stable-kernel-rules.rst index 48e88e5ad2c5..4f206cee31a7 100644

Documentation/translations/it_IT/process/stable-kernel-rules.rst +0 -0
@@ -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

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:

https://patchwork.ozlabs.org/bundle/davem/stable/?series=&submitter=&state=
*&q=&archive= diff --git a/Documentation/translations/zh_CN/process/4.Coding.rst b/Documentation/translations/zh_CN/process/4.Coding.rst index 5301e9d55255..8bb777941394 100644

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>` 描述了内核的所有引导时间参数。任何添加新参数的补丁都应该向该文件添加适当的

(quoted diff) +0 -0

b/Documentation/x86/x86_64/5level-paging.rst index ab88a4514163..44856417e6a5 100644

Documentation/x86/x86_64/5level-paging.rst +0 -0
@@ -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/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.rst index
2f69836b8445..6a4285a3c7a4 100644

Documentation/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 runtime

tunables. +Please see Documentation/x86/x86_64/machinecheck.rst for sysfs runtime tunables.

mce=off

Documentation/x86/x86_64/boot-options.rst +1 -1
 		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
(quoted diff) +0 -0

b/Documentation/x86/x86_64/fake-numa-for-cpusets.rst index 74fbb78b3c67..04df57b9aa3f 100644

Documentation/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, 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 diff --git a/MAINTAINERS b/MAINTAINERS
index 5cfbea4ce575..a38d7273705a 100644

MAINTAINERS +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.txt

MAINTAINERS +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
index 8869742a85df..0f220264cc23 100644

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.c index 07bf740bea91..31cc2f423aa8 100644

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

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
index 8c1c636308c8..e868d2bd48b8 100644
@@ -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 -1
 	  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 +0 -0
index 2bbbd4d1ba31..78fdf2dd71d1 100644
@@ -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 -1
 	  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

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 is

described - 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 enable
CONFIG_BLK_DEV_INITRD in 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 -0
 	  should'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 more

information. 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 -2
 	  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.
 

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 -1
 	  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
index f730680dc818..59f598543203 100644
@@ -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 +0 -0
index 850b8762e889..90d791ca1a95 100644
@@ -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 loadflags
arch/x86/entry/entry_64.S +1 -1
index 11aa3b2afa4d..33f9fc38d014 100644
@@ -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.h index f6f6ef436599..101eb944f13c 100644

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.
(quoted diff) +0 -0

b/arch/x86/include/asm/page_64_types.h index 793c14c372cb..288b065955b7 100644

arch/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 memory

map. */

#define __PHYSICAL_MASK_SHIFT 52

(quoted diff) +0 -0

b/arch/x86/include/asm/pgtable_64_types.h index 88bca456da99..52e5f5f2240d 100644

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

(quoted diff) +0 -0

b/arch/x86/kernel/cpu/microcode/amd.c index e1f3ba19ba54..06d4e67f31ab 100644

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";
(quoted diff) +0 -0

b/arch/x86/kernel/kexec-bzimage64.c index 22f60dd26460..b07e7069b09e 100644

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
index dcd272dbd0a9..f62b498b18fb 100644
@@ -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
index 7f61431c75fb..400c1ba033aa 100644
@@ -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.c index 1861a2ba0f2b..c0a502f7e3a7 100644

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
index 283ee94224c6..2438f37f2ca1 100644
@@ -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 -0
 	  via 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 -1
 	  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

drivers/acpi/Kconfig config ACPI_TABLE_OVERRIDE_VIA_BUILTIN_INITRD · line 365

Quoted 5 lines
drivers/acpi/Kconfig +0 -0
 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

drivers/acpi/Kconfig config ACPI_TABLE_OVERRIDE_VIA_BUILTIN_INITRD

Quoted 4 lines
drivers/acpi/Kconfig +1 -1
 	  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

drivers/acpi/Kconfig config ACPI_DEBUG · line 376

Quoted 7 lines
drivers/acpi/Kconfig +0 -0
 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

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.rst to 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 -1
 	  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

drivers/acpi/Kconfig config ACPI_CUSTOM_METHOD · line 451

Quoted 1 line
drivers/acpi/Kconfig +0 -0
 	  kernel 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.c index b17b79e612a3..ac6280ad43a1 100644

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);
 
(quoted diff) +0 -0

b/drivers/staging/fieldbus/Documentation/fieldbus_dev.txt index 56af3f650fa3..89fb8e14676f 100644

drivers/staging/fieldbus/Documentation/fieldbus_dev.txt +0 -0
@@ -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:

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 get

their diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c index 1e3ed41ae1f3..69938dbae2d0 100644

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
index de1804aeaf69..98e3db7a89cd 100644
@@ -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 +0 -0
index 1f966670c8dc..623eb58560b9 100644
@@ -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 {

include/linux/fs_context.h +0 -0
 	const struct fs_context_operations *ops;
include/linux/lsm_hooks.h +0 -0
index 47f58cfb6a19..df1318d85f7d 100644

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
index ee8d1f311858..6e5fb81bde4b 100644
@@ -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 -0
 	  determines what happens to newly added memory regions. Policy 

setting

Quoted 6 lines
mm/Kconfig +1 -1
 	  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

Quoted 51 lines
mm/Kconfig +0 -0
 	  'online' state by default.
security/Kconfig +1 -1
index aeac3676dd4d..6d75ed71970c 100644
@@ -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
index 2f5a12b88a86..25f2bb3a991d 100644
@@ -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.txt index 4dd11a554b9b..de094670050b 100644

tools/objtool/Documentation/stack-validation.txt +0 -0
@@ -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

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 16 lines
Quoted 9 lines
(quoted diff) +0 -0

b/tools/testing/selftests/x86/protection_keys.c index 5d546dcdbc80..798a5ddeee55 100644

tools/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 (see Documentation/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

maintainer Acked-by
#48 lore raw

Re: [PATCH 22/22] docs: fix broken documentation links

In reply to Federico Vaga
Quoted 6 lines · Federico Vaga
Quoted 2 lines · CEST Mauro Carvalho Chehab

Mostly due to x86 and acpi conversion, several documentation links are still pointing to the old file. Fix them.

For the Italian documentation I just send I patch to fix them in a dedicated patch

for the vhost change.

Quoted 1,005 lines
Quoted 70 lines
---
 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/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 +-
 48 files changed, 77 insertions(+), 78 deletions(-)
(quoted diff) +0 -0

b/Documentation/acpi/dsd/leds.txt index 81a63af42ed2..cc58b1a574c5 100644

Documentation/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.rst index 0124980dca2d..8d3273e32eb1 100644

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 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

Documentation/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.txt index 138f6664b2e2..4a02d1346635 100644

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 -0
 			debug 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 -0
 			information 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 -0
 			multiple 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 -0
 			vendor 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 -1
 	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

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 -0
 	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

Documentation/admin-guide/kernel-parameters.txt

Quoted 3 lines
Documentation/admin-guide/kernel-parameters.txt +1 -1
 			option.
-			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 -0
 	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

Documentation/admin-guide/kernel-parameters.txt

Quoted 3 lines
Documentation/admin-guide/kernel-parameters.txt +0 -1
 			mem_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/virtual/kvm/amd-

memory-encryption.rst

Documentation/admin-guide/kernel-parameters.txt line 2532

Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +0 -0
 			for 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 -1
 	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.

Documentation/admin-guide/kernel-parameters.txt line 5055

Quoted 2 lines
Documentation/admin-guide/kernel-parameters.txt +0 -0
 	vga=		[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.rst index c7495e42e6f4..2b20f5f7380d 100644

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
 *************************************
(quoted diff) +0 -0

b/Documentation/devicetree/bindings/net/fsl-enetc.txt index c812e25ae90f..25fc687419db 100644

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:
 
(quoted diff) +0 -0

b/Documentation/devicetree/bindings/pci/amlogic,meson-pcie.txt index 12b18f82d441..efa2c8b9b85a 100644

Documentation/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 PCI

core. 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.txt b/Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txt index 7ef2dbe48e8a..14d2eee96b3d 100644

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 264 lines
Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txt +1 -1
 		    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 diff --git a/Documentation/devicetree/booting-without-of.txt b/Documentation/devicetree/booting-without-of.txt index e86bd2f64117..60f8640f2b2f 100644

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
(quoted diff) +0 -0

b/Documentation/driver-api/gpio/board.rst index b37f3f7b8926..ce91518bf9f4 100644

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
 -------------
(quoted diff) +0 -0

b/Documentation/driver-api/gpio/consumer.rst index 5e4d8aa68913..fdecb6d711db 100644

Documentation/driver-api/gpio/consumer.rst +0 -0
@@ -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.

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.rst index 850be9696931..1252617b520f 100644

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

(quoted diff) +0 -0

b/Documentation/firmware-guide/acpi/method-tracing.rst index d0b077b73f5f..0aa7e2c5d32a 100644

Documentation/firmware-guide/acpi/method-tracing.rst +0 -0
@@ -68,7 +68,7 @@ c. Filter out the debug layer/level matched logs when the

specified

Where:

    0xXXXXXXXX/0xYYYYYYYY
Documentation/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 possible

debug 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 -0

b/Documentation/i2c/instantiating-devices index 0d85ac1935b7..5a3e2f331e8c 100644

Documentation/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. +which

is currently located at Documentation/firmware-guide/acpi/enumeration.rst.

Method 2: Instantiate the devices explicitly

(quoted diff) +0 -0

b/Documentation/sysctl/kernel.txt index f0c86fbb3b48..92f7f34b021a 100644

Documentation/sysctl/kernel.txt +0 -0
@@ -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/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 example

above, this file will contain the value 564 = 0x234.

See the type_of_loader and ext_loader_ver fields in

Documentation/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/howto.rst index 9903ac7c566b..44e6077730e8 100644

Documentation/translations/it_IT/process/howto.rst +0 -0
@@ -131,7 +131,7 @@ Di seguito una lista di file che sono presenti nei

sorgente del kernel e che "Linux kernel patch submission format"

Documentation/translations/it_IT/process/howto.rst +0 -1
 		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: diff --git a/Documentation/translations/it_IT/process/stable-kernel-rules.rst b/Documentation/translations/it_IT/process/stable-kernel-rules.rst index 48e88e5ad2c5..4f206cee31a7 100644

Documentation/translations/it_IT/process/stable-kernel-rules.rst +0 -0
@@ -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

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:

https://patchwork.ozlabs.org/bundle/davem/stable/?series=&submitter=&state=
*&q=&archive= diff --git a/Documentation/translations/zh_CN/process/4.Coding.rst b/Documentation/translations/zh_CN/process/4.Coding.rst index 5301e9d55255..8bb777941394 100644

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>` 描述了内核的所有引导时间参数。任何添加新参数的补丁都应该向该文件添加适当的

(quoted diff) +0 -0

b/Documentation/x86/x86_64/5level-paging.rst index ab88a4514163..44856417e6a5 100644

Documentation/x86/x86_64/5level-paging.rst +0 -0
@@ -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/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.rst index
2f69836b8445..6a4285a3c7a4 100644

Documentation/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 runtime

tunables. +Please see Documentation/x86/x86_64/machinecheck.rst for sysfs runtime tunables.

mce=off

Documentation/x86/x86_64/boot-options.rst +1 -1
 		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
(quoted diff) +0 -0

b/Documentation/x86/x86_64/fake-numa-for-cpusets.rst index 74fbb78b3c67..04df57b9aa3f 100644

Documentation/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, 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 diff --git a/MAINTAINERS b/MAINTAINERS
index 5cfbea4ce575..a38d7273705a 100644

MAINTAINERS +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.txt

MAINTAINERS +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
index 8869742a85df..0f220264cc23 100644

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.c index 07bf740bea91..31cc2f423aa8 100644

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

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
index 8c1c636308c8..e868d2bd48b8 100644
@@ -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 -1
 	  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 +0 -0
index 2bbbd4d1ba31..78fdf2dd71d1 100644
@@ -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 -1
 	  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

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 is

described - 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 enable
CONFIG_BLK_DEV_INITRD in 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 -0
 	  should'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 more

information. 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 -2
 	  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.
 

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 -1
 	  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
index f730680dc818..59f598543203 100644
@@ -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 +0 -0
index 850b8762e889..90d791ca1a95 100644
@@ -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 loadflags
arch/x86/entry/entry_64.S +1 -1
index 11aa3b2afa4d..33f9fc38d014 100644
@@ -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.h index f6f6ef436599..101eb944f13c 100644

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.
(quoted diff) +0 -0

b/arch/x86/include/asm/page_64_types.h index 793c14c372cb..288b065955b7 100644

arch/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 memory

map. */

#define __PHYSICAL_MASK_SHIFT 52

(quoted diff) +0 -0

b/arch/x86/include/asm/pgtable_64_types.h index 88bca456da99..52e5f5f2240d 100644

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

(quoted diff) +0 -0

b/arch/x86/kernel/cpu/microcode/amd.c index e1f3ba19ba54..06d4e67f31ab 100644

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";
(quoted diff) +0 -0

b/arch/x86/kernel/kexec-bzimage64.c index 22f60dd26460..b07e7069b09e 100644

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
index dcd272dbd0a9..f62b498b18fb 100644
@@ -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
index 7f61431c75fb..400c1ba033aa 100644
@@ -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.c index 1861a2ba0f2b..c0a502f7e3a7 100644

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
index 283ee94224c6..2438f37f2ca1 100644
@@ -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 -0
 	  via 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 -1
 	  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

drivers/acpi/Kconfig config ACPI_TABLE_OVERRIDE_VIA_BUILTIN_INITRD · line 365

Quoted 5 lines
drivers/acpi/Kconfig +0 -0
 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

drivers/acpi/Kconfig config ACPI_TABLE_OVERRIDE_VIA_BUILTIN_INITRD

Quoted 4 lines
drivers/acpi/Kconfig +1 -1
 	  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

drivers/acpi/Kconfig config ACPI_DEBUG · line 376

Quoted 7 lines
drivers/acpi/Kconfig +0 -0
 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

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.rst to 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 -1
 	  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

drivers/acpi/Kconfig config ACPI_CUSTOM_METHOD · line 451

Quoted 1 line
drivers/acpi/Kconfig +0 -0
 	  kernel 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.c index b17b79e612a3..ac6280ad43a1 100644

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);
 
(quoted diff) +0 -0

b/drivers/staging/fieldbus/Documentation/fieldbus_dev.txt index 56af3f650fa3..89fb8e14676f 100644

drivers/staging/fieldbus/Documentation/fieldbus_dev.txt +0 -0
@@ -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:

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 get

their diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c index 1e3ed41ae1f3..69938dbae2d0 100644

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
index de1804aeaf69..98e3db7a89cd 100644
@@ -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 +0 -0
index 1f966670c8dc..623eb58560b9 100644
@@ -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 {

include/linux/fs_context.h +0 -0
 	const struct fs_context_operations *ops;
include/linux/lsm_hooks.h +0 -0
index 47f58cfb6a19..df1318d85f7d 100644

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
index ee8d1f311858..6e5fb81bde4b 100644
@@ -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 -0
 	  determines what happens to newly added memory regions. Policy 

setting

Quoted 6 lines
mm/Kconfig +1 -1
 	  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

Quoted 51 lines
mm/Kconfig +0 -0
 	  'online' state by default.
security/Kconfig +1 -1
index aeac3676dd4d..6d75ed71970c 100644
@@ -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
index 2f5a12b88a86..25f2bb3a991d 100644
@@ -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.txt index 4dd11a554b9b..de094670050b 100644

tools/objtool/Documentation/stack-validation.txt +0 -0
@@ -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

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 16 lines
Quoted 9 lines
(quoted diff) +0 -0

b/tools/testing/selftests/x86/protection_keys.c index 5d546dcdbc80..798a5ddeee55 100644

tools/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 (see Documentation/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

maintainer
#49 lore raw

Re: [PATCH 22/22] docs: fix broken documentation links

In reply to Mauro Carvalho Chehab
Quoted 2 lines · CEST Mauro Carvalho Chehab

Mostly due to x86 and acpi conversion, several documentation links are still pointing to the old file. Fix them.

For the Italian documentation I just send I patch to fix them in a dedicated patch

Quoted 70 lines
---
 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/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 +-
 48 files changed, 77 insertions(+), 78 deletions(-)
(quoted diff) +0 -0

b/Documentation/acpi/dsd/leds.txt index 81a63af42ed2..cc58b1a574c5 100644

Documentation/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.rst index 0124980dca2d..8d3273e32eb1 100644

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 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

Documentation/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.txt index 138f6664b2e2..4a02d1346635 100644

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 -0
 			debug 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 -0
 			information 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 -0
 			multiple 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 -0
 			vendor 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 -1
 	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

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 -0
 	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

Documentation/admin-guide/kernel-parameters.txt

Quoted 3 lines
Documentation/admin-guide/kernel-parameters.txt +1 -1
 			option.
-			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 -0
 	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

Documentation/admin-guide/kernel-parameters.txt

Quoted 3 lines
Documentation/admin-guide/kernel-parameters.txt +0 -1
 			mem_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/virtual/kvm/amd-

memory-encryption.rst

Documentation/admin-guide/kernel-parameters.txt line 2532

Quoted 1 line
Documentation/admin-guide/kernel-parameters.txt +0 -0
 			for 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 -1
 	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.

Documentation/admin-guide/kernel-parameters.txt line 5055

Quoted 2 lines
Documentation/admin-guide/kernel-parameters.txt +0 -0
 	vga=		[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.rst index c7495e42e6f4..2b20f5f7380d 100644

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
 *************************************
(quoted diff) +0 -0

b/Documentation/devicetree/bindings/net/fsl-enetc.txt index c812e25ae90f..25fc687419db 100644

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:
 
(quoted diff) +0 -0

b/Documentation/devicetree/bindings/pci/amlogic,meson-pcie.txt index 12b18f82d441..efa2c8b9b85a 100644

Documentation/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 PCI

core. 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.txt b/Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txt index 7ef2dbe48e8a..14d2eee96b3d 100644

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 264 lines
Documentation/devicetree/bindings/regulator/qcom,rpmh-regulator.txt +1 -1
 		    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 diff --git a/Documentation/devicetree/booting-without-of.txt b/Documentation/devicetree/booting-without-of.txt index e86bd2f64117..60f8640f2b2f 100644

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
(quoted diff) +0 -0

b/Documentation/driver-api/gpio/board.rst index b37f3f7b8926..ce91518bf9f4 100644

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
 -------------
(quoted diff) +0 -0

b/Documentation/driver-api/gpio/consumer.rst index 5e4d8aa68913..fdecb6d711db 100644

Documentation/driver-api/gpio/consumer.rst +0 -0
@@ -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.

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.rst index 850be9696931..1252617b520f 100644

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

(quoted diff) +0 -0

b/Documentation/firmware-guide/acpi/method-tracing.rst index d0b077b73f5f..0aa7e2c5d32a 100644

Documentation/firmware-guide/acpi/method-tracing.rst +0 -0
@@ -68,7 +68,7 @@ c. Filter out the debug layer/level matched logs when the

specified

Where:

    0xXXXXXXXX/0xYYYYYYYY
Documentation/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 possible

debug 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 -0

b/Documentation/i2c/instantiating-devices index 0d85ac1935b7..5a3e2f331e8c 100644

Documentation/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. +which

is currently located at Documentation/firmware-guide/acpi/enumeration.rst.

Method 2: Instantiate the devices explicitly

(quoted diff) +0 -0

b/Documentation/sysctl/kernel.txt index f0c86fbb3b48..92f7f34b021a 100644

Documentation/sysctl/kernel.txt +0 -0
@@ -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/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 example

above, this file will contain the value 564 = 0x234.

See the type_of_loader and ext_loader_ver fields in

Documentation/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/howto.rst index 9903ac7c566b..44e6077730e8 100644

Documentation/translations/it_IT/process/howto.rst +0 -0
@@ -131,7 +131,7 @@ Di seguito una lista di file che sono presenti nei

sorgente del kernel e che "Linux kernel patch submission format"

Documentation/translations/it_IT/process/howto.rst +0 -1
 		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: diff --git a/Documentation/translations/it_IT/process/stable-kernel-rules.rst b/Documentation/translations/it_IT/process/stable-kernel-rules.rst index 48e88e5ad2c5..4f206cee31a7 100644

Documentation/translations/it_IT/process/stable-kernel-rules.rst +0 -0
@@ -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

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:

https://patchwork.ozlabs.org/bundle/davem/stable/?series=&submitter=&state=
*&q=&archive= diff --git a/Documentation/translations/zh_CN/process/4.Coding.rst b/Documentation/translations/zh_CN/process/4.Coding.rst index 5301e9d55255..8bb777941394 100644

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>` 描述了内核的所有引导时间参数。任何添加新参数的补丁都应该向该文件添加适当的

(quoted diff) +0 -0

b/Documentation/x86/x86_64/5level-paging.rst index ab88a4514163..44856417e6a5 100644

Documentation/x86/x86_64/5level-paging.rst +0 -0
@@ -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/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.rst index
2f69836b8445..6a4285a3c7a4 100644

Documentation/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 runtime

tunables. +Please see Documentation/x86/x86_64/machinecheck.rst for sysfs runtime tunables.

mce=off

Documentation/x86/x86_64/boot-options.rst +1 -1
 		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
(quoted diff) +0 -0

b/Documentation/x86/x86_64/fake-numa-for-cpusets.rst index 74fbb78b3c67..04df57b9aa3f 100644

Documentation/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, 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 diff --git a/MAINTAINERS b/MAINTAINERS
index 5cfbea4ce575..a38d7273705a 100644

MAINTAINERS +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.txt

MAINTAINERS +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
index 8869742a85df..0f220264cc23 100644

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.c index 07bf740bea91..31cc2f423aa8 100644

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

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
index 8c1c636308c8..e868d2bd48b8 100644
@@ -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 -1
 	  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 +0 -0
index 2bbbd4d1ba31..78fdf2dd71d1 100644
@@ -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 -1
 	  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

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 is

described - 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 enable
CONFIG_BLK_DEV_INITRD in 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 -0
 	  should'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 more

information. 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 -2
 	  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.
 

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 -1
 	  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
index f730680dc818..59f598543203 100644
@@ -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 +0 -0
index 850b8762e889..90d791ca1a95 100644
@@ -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 loadflags
arch/x86/entry/entry_64.S +1 -1
index 11aa3b2afa4d..33f9fc38d014 100644
@@ -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.h index f6f6ef436599..101eb944f13c 100644

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.
(quoted diff) +0 -0

b/arch/x86/include/asm/page_64_types.h index 793c14c372cb..288b065955b7 100644

arch/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 memory

map. */

#define __PHYSICAL_MASK_SHIFT 52

(quoted diff) +0 -0

b/arch/x86/include/asm/pgtable_64_types.h index 88bca456da99..52e5f5f2240d 100644

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

(quoted diff) +0 -0

b/arch/x86/kernel/cpu/microcode/amd.c index e1f3ba19ba54..06d4e67f31ab 100644

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";
(quoted diff) +0 -0

b/arch/x86/kernel/kexec-bzimage64.c index 22f60dd26460..b07e7069b09e 100644

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
index dcd272dbd0a9..f62b498b18fb 100644
@@ -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
index 7f61431c75fb..400c1ba033aa 100644
@@ -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.c index 1861a2ba0f2b..c0a502f7e3a7 100644

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
index 283ee94224c6..2438f37f2ca1 100644
@@ -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 -0
 	  via 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 -1
 	  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

drivers/acpi/Kconfig config ACPI_TABLE_OVERRIDE_VIA_BUILTIN_INITRD · line 365

Quoted 5 lines
drivers/acpi/Kconfig +0 -0
 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

drivers/acpi/Kconfig config ACPI_TABLE_OVERRIDE_VIA_BUILTIN_INITRD

Quoted 4 lines
drivers/acpi/Kconfig +1 -1
 	  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

drivers/acpi/Kconfig config ACPI_DEBUG · line 376

Quoted 7 lines
drivers/acpi/Kconfig +0 -0
 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

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.rst to 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 -1
 	  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

drivers/acpi/Kconfig config ACPI_CUSTOM_METHOD · line 451

Quoted 1 line
drivers/acpi/Kconfig +0 -0
 	  kernel 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.c index b17b79e612a3..ac6280ad43a1 100644

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);
 
(quoted diff) +0 -0

b/drivers/staging/fieldbus/Documentation/fieldbus_dev.txt index 56af3f650fa3..89fb8e14676f 100644

drivers/staging/fieldbus/Documentation/fieldbus_dev.txt +0 -0
@@ -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:

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 get

their diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c index 1e3ed41ae1f3..69938dbae2d0 100644

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
index de1804aeaf69..98e3db7a89cd 100644
@@ -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 +0 -0
index 1f966670c8dc..623eb58560b9 100644
@@ -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 {

include/linux/fs_context.h +0 -0
 	const struct fs_context_operations *ops;
include/linux/lsm_hooks.h +0 -0
index 47f58cfb6a19..df1318d85f7d 100644

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
index ee8d1f311858..6e5fb81bde4b 100644
@@ -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 -0
 	  determines what happens to newly added memory regions. Policy 

setting

Quoted 6 lines
mm/Kconfig +1 -1
 	  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

Quoted 60 lines
mm/Kconfig +0 -0
 	  'online' state by default.
security/Kconfig +1 -1
index aeac3676dd4d..6d75ed71970c 100644
@@ -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
index 2f5a12b88a86..25f2bb3a991d 100644
@@ -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.txt index 4dd11a554b9b..de094670050b 100644

tools/objtool/Documentation/stack-validation.txt +0 -0
@@ -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

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.c index 5d546dcdbc80..798a5ddeee55 100644

tools/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 (see Documentation/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

#50 lore raw

Re: [PATCH 22/22] docs: fix broken documentation links

In reply to Mauro Carvalho Chehab

Le 30/05/2019 à 01:23, Mauro Carvalho Chehab a écrit :

Quoted 54 lines

Mostly 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/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 +-
  48 files changed, 77 insertions(+), 78 deletions(-)

[...]

arch/powerpc/Kconfig config PPC_MEM_KEYS · line 901

Quoted 10 lines
arch/powerpc/Kconfig +1 -1
index 8c1c636308c8..e868d2bd48b8 100644
@@ -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

It looks strange to reference an x86 file, for powerpc arch.

Christophe

#51 lore raw

Re: [PATCH 22/22] docs: fix broken documentation links

Em Mon, 3 Jun 2019 09:34:15 +0200
Christophe Leroy <[email protected]> escreveu:

Quoted 66 lines

Le 30/05/2019 à 01:23, Mauro Carvalho Chehab a écrit :

Quoted 54 lines

Mostly 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/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 +-
  48 files changed, 77 insertions(+), 78 deletions(-)  

[...]

Quoted 8 lines
arch/powerpc/Kconfig +0 -0
index 8c1c636308c8..e868d2bd48b8 100644
@@ -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.
 
Quoted 4 lines

arch/powerpc/Kconfig config PPC_MEM_KEYS · line 901

Quoted 2 lines
arch/powerpc/Kconfig +1 -1
-	  For details, see Documentation/vm/protection-keys.rst
+	  For details, see Documentation/x86/protection-keys.rst  

It looks strange to reference an x86 file, for powerpc arch.

Indeed. Yet, seeking for the API documented there:

 $ git grep -l pkey_mprotect
Documentation/x86/protection-keys.rst
arch/alpha/kernel/syscalls/syscall.tbl
arch/arm/tools/syscall.tbl
arch/arm64/include/asm/unistd32.h
arch/ia64/kernel/syscalls/syscall.tbl
arch/m68k/kernel/syscalls/syscall.tbl
arch/microblaze/kernel/syscalls/syscall.tbl
arch/mips/kernel/syscalls/syscall_n32.tbl
arch/mips/kernel/syscalls/syscall_n64.tbl
arch/mips/kernel/syscalls/syscall_o32.tbl
arch/parisc/kernel/syscalls/syscall.tbl
arch/powerpc/kernel/syscalls/syscall.tbl
arch/s390/kernel/syscalls/syscall.tbl
arch/sh/kernel/syscalls/syscall.tbl
arch/sparc/kernel/syscalls/syscall.tbl
arch/x86/entry/syscalls/syscall_32.tbl
arch/x86/entry/syscalls/syscall_64.tbl
arch/xtensa/kernel/syscalls/syscall.tbl
include/linux/syscalls.h
include/uapi/asm-generic/unistd.h
kernel/sys_ni.c
mm/mprotect.c
tools/include/uapi/asm-generic/unistd.h
tools/perf/arch/powerpc/entry/syscalls/syscall.tbl
tools/perf/arch/x86/entry/syscalls/syscall_64.tbl
tools/perf/builtin-trace.c
tools/testing/selftests/x86/protection_keys.c

Despite being used on several archs, the only documentation for it is inside the x86 directory, as it seems that this is not arch-specific.

Perhaps the file should, instead, be moved to another book.

Thanks,
Mauro
_______________________________________________
Virtualization mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

#52 lore raw

Re: [PATCH 22/22] docs: fix broken documentation links

Em Tue, 4 Jun 2019 06:46:14 -0300
Mauro Carvalho Chehab <[email protected]> escreveu:

Quoted 50 lines

Em Mon, 3 Jun 2019 09:34:15 +0200
Christophe Leroy <[email protected]> escreveu:

Quoted 10 lines

[...]

Quoted 8 lines
arch/powerpc/Kconfig +0 -0
index 8c1c636308c8..e868d2bd48b8 100644
@@ -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.
 
Quoted 4 lines

arch/powerpc/Kconfig config PPC_MEM_KEYS · line 901

Quoted 2 lines
arch/powerpc/Kconfig +1 -1
-	  For details, see Documentation/vm/protection-keys.rst
+	  For details, see Documentation/x86/protection-keys.rst  

It looks strange to reference an x86 file, for powerpc arch.

Indeed. Yet, seeking for the API documented there:

 $ git grep -l pkey_mprotect
Documentation/x86/protection-keys.rst
arch/alpha/kernel/syscalls/syscall.tbl
arch/arm/tools/syscall.tbl
arch/arm64/include/asm/unistd32.h
arch/ia64/kernel/syscalls/syscall.tbl
arch/m68k/kernel/syscalls/syscall.tbl
arch/microblaze/kernel/syscalls/syscall.tbl
arch/mips/kernel/syscalls/syscall_n32.tbl
arch/mips/kernel/syscalls/syscall_n64.tbl
arch/mips/kernel/syscalls/syscall_o32.tbl
arch/parisc/kernel/syscalls/syscall.tbl
arch/powerpc/kernel/syscalls/syscall.tbl
arch/s390/kernel/syscalls/syscall.tbl
arch/sh/kernel/syscalls/syscall.tbl
arch/sparc/kernel/syscalls/syscall.tbl
arch/x86/entry/syscalls/syscall_32.tbl
arch/x86/entry/syscalls/syscall_64.tbl
arch/xtensa/kernel/syscalls/syscall.tbl
include/linux/syscalls.h
include/uapi/asm-generic/unistd.h
kernel/sys_ni.c
mm/mprotect.c
tools/include/uapi/asm-generic/unistd.h
tools/perf/arch/powerpc/entry/syscalls/syscall.tbl
tools/perf/arch/x86/entry/syscalls/syscall_64.tbl
tools/perf/builtin-trace.c
tools/testing/selftests/x86/protection_keys.c
Quoted 5 lines

Despite being used on several archs, the only documentation for it is inside the x86 directory, as it seems that this is not arch-specific.

Perhaps the file should, instead, be moved to another book.

I guess the best is to have this inside the core-api book.

Patch enclosed.

Regards,
Mauro

[PATCH] docs: move protection-keys.rst to the core-api book

This document is used by multiple architectures:

	$ echo $(git grep -l  pkey_mprotect arch|cut -d'/' -f 2|sort|uniq)
	alpha arm arm64 ia64 m68k microblaze mips parisc powerpc s390 sh sparc x86 xtensa

So, let's move it to the core book and adjust the links to it accordingly.

Documentation/core-api/index.rst +1 -0
index ee1bb8983a88..2466a4c51031 100644
@@ -34,6 +34,7 @@ Core utilities
    timekeeping
    boot-time-mm
    memory-hotplug
+   protection-keys
 
 
 Interfaces for kernel debugging
Documentation/core-api/protection-keys.rst renamed from Documentation/x86/protection-keys.rst +0 -0
similarity index 100%
rename from Documentation/x86/protection-keys.rst
rename to Documentation/core-api/protection-keys.rst
Documentation/x86/index.rst +0 -1
index ae36fc5fc649..f2de1b2d3ac7 100644
@@ -19,7 +19,6 @@ x86-specific Documentation
    tlb
    mtrr
    pat
-   protection-keys
    intel_mpx
    amd-memory-encryption
    pti
arch/powerpc/Kconfig +1 -1
index 8c1c636308c8..3b795a0cab62 100644
@@ -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/core-api/protection-keys.rst
 
 	  If unsure, say y.
 
arch/x86/Kconfig +1 -1
index 2bbbd4d1ba31..d87d53fcd261 100644
@@ -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/core-api/protection-keys.rst
 
 	  If unsure, say y.
 
tools/testing/selftests/x86/protection_keys.c +1 -1
index 5d546dcdbc80..480995bceefa 100644
@@ -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/core-api/protection-keys.rst)
  *
  * There are examples in here of:
  *  * how to set protection keys on memory
#53 lore raw

Re: [PATCH 22/22] docs: fix broken documentation links

In reply to Mauro Carvalho Chehab

Em Tue, 4 Jun 2019 06:46:14 -0300
Mauro Carvalho Chehab <[email protected]> escreveu:

Quoted 50 lines

Em Mon, 3 Jun 2019 09:34:15 +0200
Christophe Leroy <[email protected]> escreveu:

Quoted 10 lines

[...]

Quoted 8 lines
arch/powerpc/Kconfig +0 -0
index 8c1c636308c8..e868d2bd48b8 100644
@@ -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.
 
Quoted 4 lines

arch/powerpc/Kconfig config PPC_MEM_KEYS · line 901

Quoted 2 lines
arch/powerpc/Kconfig +1 -1
-	  For details, see Documentation/vm/protection-keys.rst
+	  For details, see Documentation/x86/protection-keys.rst  

It looks strange to reference an x86 file, for powerpc arch.

Indeed. Yet, seeking for the API documented there:

 $ git grep -l pkey_mprotect
Documentation/x86/protection-keys.rst
arch/alpha/kernel/syscalls/syscall.tbl
arch/arm/tools/syscall.tbl
arch/arm64/include/asm/unistd32.h
arch/ia64/kernel/syscalls/syscall.tbl
arch/m68k/kernel/syscalls/syscall.tbl
arch/microblaze/kernel/syscalls/syscall.tbl
arch/mips/kernel/syscalls/syscall_n32.tbl
arch/mips/kernel/syscalls/syscall_n64.tbl
arch/mips/kernel/syscalls/syscall_o32.tbl
arch/parisc/kernel/syscalls/syscall.tbl
arch/powerpc/kernel/syscalls/syscall.tbl
arch/s390/kernel/syscalls/syscall.tbl
arch/sh/kernel/syscalls/syscall.tbl
arch/sparc/kernel/syscalls/syscall.tbl
arch/x86/entry/syscalls/syscall_32.tbl
arch/x86/entry/syscalls/syscall_64.tbl
arch/xtensa/kernel/syscalls/syscall.tbl
include/linux/syscalls.h
include/uapi/asm-generic/unistd.h
kernel/sys_ni.c
mm/mprotect.c
tools/include/uapi/asm-generic/unistd.h
tools/perf/arch/powerpc/entry/syscalls/syscall.tbl
tools/perf/arch/x86/entry/syscalls/syscall_64.tbl
tools/perf/builtin-trace.c
tools/testing/selftests/x86/protection_keys.c
Quoted 5 lines

Despite being used on several archs, the only documentation for it is inside the x86 directory, as it seems that this is not arch-specific.

Perhaps the file should, instead, be moved to another book.

I guess the best is to have this inside the core-api book.

Patch enclosed.

Regards,
Mauro

[PATCH] docs: move protection-keys.rst to the core-api book

This document is used by multiple architectures:

	$ echo $(git grep -l  pkey_mprotect arch|cut -d'/' -f 2|sort|uniq)
	alpha arm arm64 ia64 m68k microblaze mips parisc powerpc s390 sh sparc x86 xtensa

So, let's move it to the core book and adjust the links to it accordingly.

Documentation/core-api/index.rst +1 -0
index ee1bb8983a88..2466a4c51031 100644
@@ -34,6 +34,7 @@ Core utilities
    timekeeping
    boot-time-mm
    memory-hotplug
+   protection-keys
 
 
 Interfaces for kernel debugging
Documentation/core-api/protection-keys.rst renamed from Documentation/x86/protection-keys.rst +0 -0
similarity index 100%
rename from Documentation/x86/protection-keys.rst
rename to Documentation/core-api/protection-keys.rst
Documentation/x86/index.rst +0 -1
index ae36fc5fc649..f2de1b2d3ac7 100644
@@ -19,7 +19,6 @@ x86-specific Documentation
    tlb
    mtrr
    pat
-   protection-keys
    intel_mpx
    amd-memory-encryption
    pti
arch/powerpc/Kconfig +1 -1
index 8c1c636308c8..3b795a0cab62 100644
@@ -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/core-api/protection-keys.rst
 
 	  If unsure, say y.
 
arch/x86/Kconfig +1 -1
index 2bbbd4d1ba31..d87d53fcd261 100644
@@ -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/core-api/protection-keys.rst
 
 	  If unsure, say y.
 
tools/testing/selftests/x86/protection_keys.c +1 -1
index 5d546dcdbc80..480995bceefa 100644
@@ -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/core-api/protection-keys.rst)
  *
  * There are examples in here of:
  *  * how to set protection keys on memory
#54 lore raw

Re: [PATCH 22/22] docs: fix broken documentation links

In reply to Mauro Carvalho Chehab

Le 30/05/2019 à 01:23, Mauro Carvalho Chehab a écrit :

Quoted 54 lines

Mostly 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/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 +-
  48 files changed, 77 insertions(+), 78 deletions(-)

[...]

arch/powerpc/Kconfig config PPC_MEM_KEYS · line 901

Quoted 10 lines
arch/powerpc/Kconfig +1 -1
index 8c1c636308c8..e868d2bd48b8 100644
@@ -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

It looks strange to reference an x86 file, for powerpc arch.

Christophe

_______________________________________________
Virtualization mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

maintainer Acked-by on v1 22/22
#55 lore raw

Re: [PATCH 22/22] docs: fix broken documentation links

In reply to Mauro Carvalho Chehab
Quoted 2 lines · Mauro Carvalho Chehab

Mostly due to x86 and acpi conversion, several documentation links are still pointing to the old file. Fix them.

_______________________________________________
Virtualization mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

Reviewed-by on v1 22/22
#56 lore raw

Re: [PATCH 22/22] docs: fix broken documentation links

In reply to Mauro Carvalho Chehab
Quoted 669 lines · Mauro Carvalho Chehab

Mostly 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/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 +-
  48 files changed, 77 insertions(+), 78 deletions(-)
Documentation/acpi/dsd/leds.txt +1 -1
index 81a63af42ed2..cc58b1a574c5 100644
@@ -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
index 0124980dca2d..8d3273e32eb1 100644
@@ -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
index 138f6664b2e2..4a02d1346635 100644
@@ -53,7 +53,7 @@
                      ACPI_DEBUG_PRINT statements, e.g.,
                          ACPI_DEBUG_PRINT((ACPI_DB_INFO, ...
                      The debug_level mask defaults to "info".  See
-                     Documentation/acpi/debug.txt for more information about
+                     Documentation/firmware-guide/acpi/debug.rst for more information about
                      debug layers and levels.
 
                      Enable processor driver info messages:
@@ -963,7 +963,7 @@
                      for details.
 
      nompx           [X86] Disables Intel Memory Protection Extensions.
-                     See Documentation/x86/intel_mpx.txt for more
+                     See Documentation/x86/intel_mpx.rst for more
                      information about the feature.
 
      nopku           [X86] Disable Memory Protection Keys CPU feature found
@@ -1189,7 +1189,7 @@
                      that is to be dynamically loaded by Linux. If there are
                      multiple variables with the same name but with different
                      vendor GUIDs, all of them will be loaded. See
-                     Documentation/acpi/ssdt-overlays.txt for details.
+                     Documentation/admin-guide/acpi/ssdt-overlays.rst for details.
 
 
      eisa_irq_edge=  [PARISC,HW]
@@ -2383,7 +2383,7 @@
 
      mce             [X86-32] Machine Check Exception
 
-     mce=option      [X86-64] See Documentation/x86/x86_64/boot-options.txt
+     mce=option      [X86-64] See Documentation/x86/x86_64/boot-options.rst
 
      md=             [HW] RAID subsystems devices and level
                      See Documentation/admin-guide/md.rst.
@@ -2439,7 +2439,7 @@
                      set according to the
                      CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE kernel config
                      option.
-                     See Documentation/memory-hotplug.txt.
+                     See Documentation/admin-guide/mm/memory-hotplug.rst.
 
      memmap=exactmap [KNL,X86] Enable setting of an exact
                      E820 memory map, as specified by the user.
@@ -2528,7 +2528,7 @@
                      mem_encrypt=on:         Activate SME
                      mem_encrypt=off:        Do not activate SME
 
-                     Refer to Documentation/x86/amd-memory-encryption.txt
+                     Refer to Documentation/virtual/kvm/amd-memory-encryption.rst
                      for details on when memory encryption can be activated.
 
      mem_sleep_default=      [SUSPEND] Default system suspend mode:
@@ -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
index c7495e42e6f4..2b20f5f7380d 100644
@@ -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
index c812e25ae90f..25fc687419db 100644
@@ -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
index 12b18f82d441..efa2c8b9b85a 100644
@@ -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
index 7ef2dbe48e8a..14d2eee96b3d 100644
@@ -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
index e86bd2f64117..60f8640f2b2f 100644
@@ -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
index b37f3f7b8926..ce91518bf9f4 100644
@@ -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
index 5e4d8aa68913..fdecb6d711db 100644
@@ -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
index 850be9696931..1252617b520f 100644
@@ -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
index d0b077b73f5f..0aa7e2c5d32a 100644
@@ -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
index 0d85ac1935b7..5a3e2f331e8c 100644
@@ -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
index f0c86fbb3b48..92f7f34b021a 100644
@@ -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/howto.rst +1 -1
index 9903ac7c566b..44e6077730e8 100644
@@ -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
index 48e88e5ad2c5..4f206cee31a7 100644
@@ -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
index 5301e9d55255..8bb777941394 100644
@@ -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
index ab88a4514163..44856417e6a5 100644
@@ -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
index 2f69836b8445..6a4285a3c7a4 100644
@@ -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
index 74fbb78b3c67..04df57b9aa3f 100644
@@ -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
index 5cfbea4ce575..a38d7273705a 100644
@@ -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
index 8869742a85df..0f220264cc23 100644
@@ -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
index 07bf740bea91..31cc2f423aa8 100644
@@ -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
index 8c1c636308c8..e868d2bd48b8 100644
@@ -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
index 2bbbd4d1ba31..78fdf2dd71d1 100644
@@ -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
index f730680dc818..59f598543203 100644
@@ -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
index 850b8762e889..90d791ca1a95 100644
@@ -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
index 11aa3b2afa4d..33f9fc38d014 100644
@@ -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
index f6f6ef436599..101eb944f13c 100644
@@ -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
index 793c14c372cb..288b065955b7 100644
@@ -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
index 88bca456da99..52e5f5f2240d 100644
@@ -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
index e1f3ba19ba54..06d4e67f31ab 100644
@@ -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 +0 -0
index 22f60dd26460..b07e7069b09e 100644

arch/x86/kernel/kexec-bzimage64.c static void *bzImage64_load(struct kimage *image, char *kernel, · line 420

Quoted 6 lines
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;

For the arm, arm64 and x86 kexec bits:

Thanks,
Bhupesh

Reviewed-by on v1 22/22
#57 lore raw

Re: [PATCH 22/22] docs: fix broken documentation links

In reply to Mauro Carvalho Chehab
Quoted 669 lines · Mauro Carvalho Chehab

Mostly 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/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 +-
  48 files changed, 77 insertions(+), 78 deletions(-)
Documentation/acpi/dsd/leds.txt +1 -1
index 81a63af42ed2..cc58b1a574c5 100644
@@ -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
index 0124980dca2d..8d3273e32eb1 100644
@@ -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
index 138f6664b2e2..4a02d1346635 100644
@@ -53,7 +53,7 @@
                      ACPI_DEBUG_PRINT statements, e.g.,
                          ACPI_DEBUG_PRINT((ACPI_DB_INFO, ...
                      The debug_level mask defaults to "info".  See
-                     Documentation/acpi/debug.txt for more information about
+                     Documentation/firmware-guide/acpi/debug.rst for more information about
                      debug layers and levels.
 
                      Enable processor driver info messages:
@@ -963,7 +963,7 @@
                      for details.
 
      nompx           [X86] Disables Intel Memory Protection Extensions.
-                     See Documentation/x86/intel_mpx.txt for more
+                     See Documentation/x86/intel_mpx.rst for more
                      information about the feature.
 
      nopku           [X86] Disable Memory Protection Keys CPU feature found
@@ -1189,7 +1189,7 @@
                      that is to be dynamically loaded by Linux. If there are
                      multiple variables with the same name but with different
                      vendor GUIDs, all of them will be loaded. See
-                     Documentation/acpi/ssdt-overlays.txt for details.
+                     Documentation/admin-guide/acpi/ssdt-overlays.rst for details.
 
 
      eisa_irq_edge=  [PARISC,HW]
@@ -2383,7 +2383,7 @@
 
      mce             [X86-32] Machine Check Exception
 
-     mce=option      [X86-64] See Documentation/x86/x86_64/boot-options.txt
+     mce=option      [X86-64] See Documentation/x86/x86_64/boot-options.rst
 
      md=             [HW] RAID subsystems devices and level
                      See Documentation/admin-guide/md.rst.
@@ -2439,7 +2439,7 @@
                      set according to the
                      CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE kernel config
                      option.
-                     See Documentation/memory-hotplug.txt.
+                     See Documentation/admin-guide/mm/memory-hotplug.rst.
 
      memmap=exactmap [KNL,X86] Enable setting of an exact
                      E820 memory map, as specified by the user.
@@ -2528,7 +2528,7 @@
                      mem_encrypt=on:         Activate SME
                      mem_encrypt=off:        Do not activate SME
 
-                     Refer to Documentation/x86/amd-memory-encryption.txt
+                     Refer to Documentation/virtual/kvm/amd-memory-encryption.rst
                      for details on when memory encryption can be activated.
 
      mem_sleep_default=      [SUSPEND] Default system suspend mode:
@@ -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
index c7495e42e6f4..2b20f5f7380d 100644
@@ -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
index c812e25ae90f..25fc687419db 100644
@@ -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
index 12b18f82d441..efa2c8b9b85a 100644
@@ -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
index 7ef2dbe48e8a..14d2eee96b3d 100644
@@ -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
index e86bd2f64117..60f8640f2b2f 100644
@@ -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
index b37f3f7b8926..ce91518bf9f4 100644
@@ -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
index 5e4d8aa68913..fdecb6d711db 100644
@@ -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
index 850be9696931..1252617b520f 100644
@@ -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
index d0b077b73f5f..0aa7e2c5d32a 100644
@@ -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
index 0d85ac1935b7..5a3e2f331e8c 100644
@@ -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
index f0c86fbb3b48..92f7f34b021a 100644
@@ -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/howto.rst +1 -1
index 9903ac7c566b..44e6077730e8 100644
@@ -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
index 48e88e5ad2c5..4f206cee31a7 100644
@@ -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
index 5301e9d55255..8bb777941394 100644
@@ -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
index ab88a4514163..44856417e6a5 100644
@@ -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
index 2f69836b8445..6a4285a3c7a4 100644
@@ -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
index 74fbb78b3c67..04df57b9aa3f 100644
@@ -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
index 5cfbea4ce575..a38d7273705a 100644
@@ -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
index 8869742a85df..0f220264cc23 100644
@@ -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
index 07bf740bea91..31cc2f423aa8 100644
@@ -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
index 8c1c636308c8..e868d2bd48b8 100644
@@ -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
index 2bbbd4d1ba31..78fdf2dd71d1 100644
@@ -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
index f730680dc818..59f598543203 100644
@@ -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
index 850b8762e889..90d791ca1a95 100644
@@ -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
index 11aa3b2afa4d..33f9fc38d014 100644
@@ -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
index f6f6ef436599..101eb944f13c 100644
@@ -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
index 793c14c372cb..288b065955b7 100644
@@ -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
index 88bca456da99..52e5f5f2240d 100644
@@ -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
index e1f3ba19ba54..06d4e67f31ab 100644
@@ -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 +0 -0
index 22f60dd26460..b07e7069b09e 100644

arch/x86/kernel/kexec-bzimage64.c static void *bzImage64_load(struct kimage *image, char *kernel, · line 420

Quoted 6 lines
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;

For the arm, arm64 and x86 kexec bits:

Thanks,
Bhupesh
_______________________________________________
Virtualization mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

#58 lore raw

PATCH 22/22 docs: fix broken documentation links

In reply to Mauro Carvalho Chehab

Mostly 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/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 +-
 48 files changed, 77 insertions(+), 78 deletions(-)
Documentation/acpi/dsd/leds.txt +1 -1
index 81a63af42ed2..cc58b1a574c5 100644
@@ -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
index 0124980dca2d..8d3273e32eb1 100644
@@ -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
index 138f6664b2e2..4a02d1346635 100644
@@ -53,7 +53,7 @@
 			ACPI_DEBUG_PRINT statements, e.g.,
 			    ACPI_DEBUG_PRINT((ACPI_DB_INFO, ...
 			The debug_level mask defaults to "info".  See
-			Documentation/acpi/debug.txt for more information about
+			Documentation/firmware-guide/acpi/debug.rst for more information about
 			debug layers and levels.
 
 			Enable processor driver info messages:
@@ -963,7 +963,7 @@
 			for details.
 
 	nompx		[X86] Disables Intel Memory Protection Extensions.
-			See Documentation/x86/intel_mpx.txt for more
+			See Documentation/x86/intel_mpx.rst for more
 			information about the feature.
 
 	nopku		[X86] Disable Memory Protection Keys CPU feature found
@@ -1189,7 +1189,7 @@
 			that is to be dynamically loaded by Linux. If there are
 			multiple variables with the same name but with different
 			vendor GUIDs, all of them will be loaded. See
-			Documentation/acpi/ssdt-overlays.txt for details.
+			Documentation/admin-guide/acpi/ssdt-overlays.rst for details.
 
 
 	eisa_irq_edge=	[PARISC,HW]
@@ -2383,7 +2383,7 @@
 
 	mce		[X86-32] Machine Check Exception
 
-	mce=option	[X86-64] See Documentation/x86/x86_64/boot-options.txt
+	mce=option	[X86-64] See Documentation/x86/x86_64/boot-options.rst
 
 	md=		[HW] RAID subsystems devices and level
 			See Documentation/admin-guide/md.rst.
@@ -2439,7 +2439,7 @@
 			set according to the
 			CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE kernel config
 			option.
-			See Documentation/memory-hotplug.txt.
+			See Documentation/admin-guide/mm/memory-hotplug.rst.
 
 	memmap=exactmap	[KNL,X86] Enable setting of an exact
 			E820 memory map, as specified by the user.
@@ -2528,7 +2528,7 @@
 			mem_encrypt=on:		Activate SME
 			mem_encrypt=off:	Do not activate SME
 
-			Refer to Documentation/x86/amd-memory-encryption.txt
+			Refer to Documentation/virtual/kvm/amd-memory-encryption.rst
 			for details on when memory encryption can be activated.
 
 	mem_sleep_default=	[SUSPEND] Default system suspend mode:
@@ -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
index c7495e42e6f4..2b20f5f7380d 100644
@@ -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
index c812e25ae90f..25fc687419db 100644
@@ -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
index 12b18f82d441..efa2c8b9b85a 100644
@@ -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
index 7ef2dbe48e8a..14d2eee96b3d 100644
@@ -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
index e86bd2f64117..60f8640f2b2f 100644
@@ -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
index b37f3f7b8926..ce91518bf9f4 100644
@@ -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
index 5e4d8aa68913..fdecb6d711db 100644
@@ -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
index 850be9696931..1252617b520f 100644
@@ -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
index d0b077b73f5f..0aa7e2c5d32a 100644
@@ -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
index 0d85ac1935b7..5a3e2f331e8c 100644
@@ -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
index f0c86fbb3b48..92f7f34b021a 100644
@@ -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/howto.rst +1 -1
index 9903ac7c566b..44e6077730e8 100644
@@ -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
index 48e88e5ad2c5..4f206cee31a7 100644
@@ -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
index 5301e9d55255..8bb777941394 100644
@@ -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
index ab88a4514163..44856417e6a5 100644
@@ -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
index 2f69836b8445..6a4285a3c7a4 100644
@@ -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
index 74fbb78b3c67..04df57b9aa3f 100644
@@ -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
index 5cfbea4ce575..a38d7273705a 100644
@@ -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
index 8869742a85df..0f220264cc23 100644
@@ -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
index 07bf740bea91..31cc2f423aa8 100644
@@ -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
index 8c1c636308c8..e868d2bd48b8 100644
@@ -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
index 2bbbd4d1ba31..78fdf2dd71d1 100644
@@ -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
index f730680dc818..59f598543203 100644
@@ -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
index 850b8762e889..90d791ca1a95 100644
@@ -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
index 11aa3b2afa4d..33f9fc38d014 100644
@@ -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
index f6f6ef436599..101eb944f13c 100644
@@ -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
index 793c14c372cb..288b065955b7 100644
@@ -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
index 88bca456da99..52e5f5f2240d 100644
@@ -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
index e1f3ba19ba54..06d4e67f31ab 100644
@@ -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
index 22f60dd26460..b07e7069b09e 100644
@@ -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
index dcd272dbd0a9..f62b498b18fb 100644
@@ -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
index 7f61431c75fb..400c1ba033aa 100644
@@ -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
index 1861a2ba0f2b..c0a502f7e3a7 100644
@@ -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
index 283ee94224c6..2438f37f2ca1 100644
@@ -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
index b17b79e612a3..ac6280ad43a1 100644
@@ -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
index 56af3f650fa3..89fb8e14676f 100644
@@ -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
index 1e3ed41ae1f3..69938dbae2d0 100644
@@ -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
index de1804aeaf69..98e3db7a89cd 100644
@@ -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
index 1f966670c8dc..623eb58560b9 100644
@@ -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
index 47f58cfb6a19..df1318d85f7d 100644
@@ -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
index ee8d1f311858..6e5fb81bde4b 100644
@@ -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
index aeac3676dd4d..6d75ed71970c 100644
@@ -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
index 2f5a12b88a86..25f2bb3a991d 100644
@@ -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
index 4dd11a554b9b..de094670050b 100644
@@ -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
index 5d546dcdbc80..798a5ddeee55 100644
@@ -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