Fix broken references to files under Documentation/*

Some files got renamed but probably due to some merge conflicts, a few references still point to the old locations.

Signed-off-by Mauro Carvalho Chehab <[email protected]>

Acked-by Wolfram Sang <[email protected]> # I2C part

Reviewed-by Jerry Hoemann <[email protected]> # hpwdt.rst

---
 Documentation/RCU/rculist_nulls.txt                   |  2 +-
 Documentation/devicetree/bindings/arm/idle-states.txt |  2 +-
 Documentation/locking/spinlocks.rst                   |  4 ++--
 Documentation/memory-barriers.txt                     |  2 +-
 Documentation/translations/ko_KR/memory-barriers.txt  |  2 +-
 Documentation/watchdog/hpwdt.rst                      |  2 +-
 MAINTAINERS                                           | 10 +++++-----
 drivers/gpu/drm/drm_modes.c                           |  2 +-
 drivers/i2c/busses/i2c-nvidia-gpu.c                   |  2 +-
 drivers/scsi/hpsa.c                                   |  4 ++--
 10 files changed, 16 insertions(+), 16 deletions(-)

Quoted 4 lines · Mauro Carvalho Chehab

Some files got renamed but probably due to some merge conflicts, a few references still point to the old locations.

Quoted 12 lines

Signed-off-by Mauro Carvalho Chehab <[email protected]>

Acked-by Wolfram Sang <[email protected]> # I2C part

Reviewed-by Jerry Hoemann <[email protected]> # hpwdt.rst

---
 Documentation/RCU/rculist_nulls.txt                   |  2 +-
 Documentation/devicetree/bindings/arm/idle-states.txt |  2 +-
 Documentation/locking/spinlocks.rst                   |  4 ++--
 Documentation/memory-barriers.txt                     |  2 +-
 Documentation/translations/ko_KR/memory-barriers.txt  |  2 +-
 Documentation/watchdog/hpwdt.rst                      |  2 +-
 MAINTAINERS                                           | 10 +++++-----
 drivers/gpu/drm/drm_modes.c                           |  2 +-

Quoted 3 lines

 drivers/i2c/busses/i2c-nvidia-gpu.c                   |  2 +-
 drivers/scsi/hpsa.c                                   |  4 ++--
 10 files changed, 16 insertions(+), 16 deletions(-)

Acked-by Rob Herring <[email protected]>

Some files got renamed but probably due to some merge conflicts, a few references still point to the old locations.

Signed-off-by Mauro Carvalho Chehab <[email protected]>

Acked-by Wolfram Sang <[email protected]> # I2C part

Reviewed-by Jerry Hoemann <[email protected]> # hpwdt.rst

---
 Documentation/RCU/rculist_nulls.txt                   |  2 +-
 Documentation/devicetree/bindings/arm/idle-states.txt |  2 +-
 Documentation/locking/spinlocks.rst                   |  4 ++--
 Documentation/memory-barriers.txt                     |  2 +-
 Documentation/translations/ko_KR/memory-barriers.txt  |  2 +-
 Documentation/watchdog/hpwdt.rst                      |  2 +-
 MAINTAINERS                                           | 10 +++++-----
 drivers/gpu/drm/drm_modes.c                           |  2 +-
 drivers/i2c/busses/i2c-nvidia-gpu.c                   |  2 +-
 drivers/scsi/hpsa.c                                   |  4 ++--
 10 files changed, 16 insertions(+), 16 deletions(-)

Documentation/RCU/rculist_nulls.txt +1 -1

index 8151f0195f76..23f115dc87cf 100644
@@ -1,7 +1,7 @@
 Using hlist_nulls to protect read-mostly linked lists and
 objects using SLAB_TYPESAFE_BY_RCU allocations.
 
-Please read the basics in Documentation/RCU/listRCU.txt
+Please read the basics in Documentation/RCU/listRCU.rst
 
 Using special makers (called 'nulls') is a convenient way
 to solve following problem :

Documentation/devicetree/bindings/arm/idle-states.txt +1 -1

index 326f29b270ad..2d325bed37e5 100644
@@ -703,4 +703,4 @@ cpus {
     https://www.devicetree.org/specifications/
 
 [6] ARM Linux Kernel documentation - Booting AArch64 Linux
-    Documentation/arm64/booting.txt
+    Documentation/arm64/booting.rst

Documentation/locking/spinlocks.rst +2 -2

index 098107fb7d86..e93ec6645238 100644
@@ -82,7 +82,7 @@ itself.  The read lock allows many concurrent readers.  Anything that
 **changes** the list will have to get the write lock.
 
    NOTE! RCU is better for list traversal, but requires careful
-   attention to design detail (see Documentation/RCU/listRCU.txt).
+   attention to design detail (see Documentation/RCU/listRCU.rst).
 
 Also, you cannot "upgrade" a read-lock to a write-lock, so if you at _any_
 time need to do any changes (even if you don't do it every time), you have

@@ -90,7 +90,7 @@ to get the write-lock at the very beginning.
 
    NOTE! We are working hard to remove reader-writer spinlocks in most
    cases, so please don't add a new one without consensus.  (Instead, see
-   Documentation/RCU/rcu.txt for complete information.)
+   Documentation/RCU/rcu.rst for complete information.)
 
 ----
 

Documentation/memory-barriers.txt +1 -1

index 045bb8148fe9..1adbb8a371c7 100644
@@ -548,7 +548,7 @@ There are certain things that the Linux kernel memory barriers do not guarantee:
 
 	[*] For information on bus mastering DMA and coherency please read:
 
-	    Documentation/PCI/pci.rst
+	    Documentation/driver-api/pci/pci.rst
 	    Documentation/DMA-API-HOWTO.txt
 	    Documentation/DMA-API.txt
 

Documentation/translations/ko_KR/memory-barriers.txt +1 -1

index a33c2a536542..2774624ee843 100644
@@ -569,7 +569,7 @@ ACQUIRE 는 해당 오퍼레이션의 로드 부분에만 적용되고 RELEASE 
 
 	[*] 버스 마스터링 DMA 와 일관성에 대해서는 다음을 참고하시기 바랍니다:
 
-	    Documentation/PCI/pci.rst
+	    Documentation/driver-api/pci/pci.rst
 	    Documentation/DMA-API-HOWTO.txt
 	    Documentation/DMA-API.txt
 

Documentation/watchdog/hpwdt.rst +1 -1

index c165d92cfd12..c824cd7f6e32 100644
@@ -63,7 +63,7 @@ Last reviewed: 08/20/2018
  and loop forever.  This is generally not what a watchdog user wants.
 
  For those wishing to learn more please see:
-	Documentation/kdump/kdump.rst
+	Documentation/admin-guide/kdump/kdump.rst
 	Documentation/admin-guide/kernel-parameters.txt (panic=)
 	Your Linux Distribution specific documentation.
 

MAINTAINERS +5 -5

index 4e2a525e22c0..51bdbd230174 100644
@@ -899,7 +899,7 @@ L:	[email protected]
 W:	http://ez.analog.com/community/linux-device-drivers
 S:	Supported
 F:	drivers/iio/adc/ad7124.c
-F:	Documentation/devicetree/bindings/iio/adc/adi,ad7124.txt
+F:	Documentation/devicetree/bindings/iio/adc/adi,ad7124.yaml
 
 ANALOG DEVICES INC AD7606 DRIVER
 M:	Stefan Popa <[email protected]>

@@ -4190,7 +4190,7 @@ M:	Jens Axboe <[email protected]>
 L:	[email protected]
 L:	[email protected]
 T:	git git://git.kernel.dk/linux-block
-F:	Documentation/cgroup-v1/blkio-controller.rst
+F:	Documentation/admin-guide/cgroup-v1/blkio-controller.rst
 F:	block/blk-cgroup.c
 F:	include/linux/blk-cgroup.h
 F:	block/blk-throttle.c

@@ -6317,7 +6317,7 @@ FLEXTIMER FTM-QUADDEC DRIVER
 M:	Patrick Havelange <[email protected]>
 L:	[email protected]
 S:	Maintained
-F:	Documentation/ABI/testing/sysfs-bus-counter-ftm-quadddec
+F:	Documentation/ABI/testing/sysfs-bus-counter-ftm-quaddec
 F:	Documentation/devicetree/bindings/counter/ftm-quaddec.txt
 F:	drivers/counter/ftm-quaddec.c
 

@@ -6856,7 +6856,7 @@ R:	Sagi Shahar <[email protected]>
 R:	Jon Olson <[email protected]>
 L:	[email protected]
 S:	Supported
-F:	Documentation/networking/device_drivers/google/gve.txt
+F:	Documentation/networking/device_drivers/google/gve.rst
 F:	drivers/net/ethernet/google
 
 GPD POCKET FAN DRIVER

@@ -12137,7 +12137,7 @@ M:	Thomas Hellstrom <[email protected]>
 M:	"VMware, Inc." <[email protected]>
 L:	[email protected]
 S:	Supported
-F:	Documentation/virt/paravirt_ops.txt
+F:	Documentation/virt/paravirt_ops.rst
 F:	arch/*/kernel/paravirt*
 F:	arch/*/include/asm/paravirt*.h
 F:	include/linux/hypervisor.h

drivers/gpu/drm/drm_modes.c +1 -1

index 74a5739df506..80fcd5dc1558 100644
@@ -1686,7 +1686,7 @@ static int drm_mode_parse_cmdline_options(char *str, size_t len,
  *
  * Additionals options can be provided following the mode, using a comma to
  * separate each option. Valid options can be found in
- * Documentation/fb/modedb.txt.
+ * Documentation/fb/modedb.rst.
  *
  * The intermediate drm_cmdline_mode structure is required to store additional
  * options from the command line modline like the force-enable/disable flag.

drivers/i2c/busses/i2c-nvidia-gpu.c +1 -1

index cfc76b5de726..5a1235fd86bb 100644
@@ -364,7 +364,7 @@ static void gpu_i2c_remove(struct pci_dev *pdev)
 /*
  * We need gpu_i2c_suspend() even if it is stub, for runtime pm to work
  * correctly. Without it, lspci shows runtime pm status as "D0" for the card.
- * Documentation/power/pci.txt also insists for driver to provide this.
+ * Documentation/power/pci.rst also insists for driver to provide this.
  */
 static __maybe_unused int gpu_i2c_suspend(struct device *dev)
 {

drivers/scsi/hpsa.c +2 -2

index 43a6b5350775..eaf6177ac9ee 100644
@@ -7798,7 +7798,7 @@ static void hpsa_free_pci_init(struct ctlr_info *h)
 	hpsa_disable_interrupt_mode(h);		/* pci_init 2 */
 	/*
 	 * call pci_disable_device before pci_release_regions per
-	 * Documentation/PCI/pci.rst
+	 * Documentation/driver-api/pci/pci.rst
 	 */
 	pci_disable_device(h->pdev);		/* pci_init 1 */
 	pci_release_regions(h->pdev);		/* pci_init 2 */

@@ -7881,7 +7881,7 @@ static int hpsa_pci_init(struct ctlr_info *h)
 clean1:
 	/*
 	 * call pci_disable_device before pci_release_regions per
-	 * Documentation/PCI/pci.rst
+	 * Documentation/driver-api/pci/pci.rst
 	 */
 	pci_disable_device(h->pdev);
 	pci_release_regions(h->pdev);

Signature · 1 line

2.21.0

There are two references to the generic counter ABI, with was added on a separate patch. Both point to a non-existing file.

Fix them.

Fixes ea2b23b89579 ("counter: Documentation: Add Generic Counter sysfs documentation")

Fixes 09e7d4ed8991 ("docs: Add Generic Counter interface documentation")

Signed-off-by Mauro Carvalho Chehab <[email protected]>

---
 Documentation/driver-api/generic-counter.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

Documentation/driver-api/generic-counter.rst +2 -2

index 0c161b1a3be6..8382f01a53e3 100644
@@ -233,7 +233,7 @@ Userspace Interface
 Several sysfs attributes are generated by the Generic Counter interface,
 and reside under the /sys/bus/counter/devices/counterX directory, where
 counterX refers to the respective counter device. Please see
-Documentation/ABI/testing/sys-bus-counter-generic-sysfs for detailed
+Documentation/ABI/testing/sysfs-bus-counter for detailed
 information on each Generic Counter interface sysfs attribute.
 
 Through these sysfs attributes, programs and scripts may interact with

@@ -325,7 +325,7 @@ sysfs attributes, where Y is the unique ID of the respective Count:
 
 For a more detailed breakdown of the available Generic Counter interface
 sysfs attributes, please refer to the
-Documentation/ABI/testing/sys-bus-counter file.
+Documentation/ABI/testing/sysfs-bus-counter file.
 
 The Signals and Counts associated with the Counter device are registered
 to the system as well by the counter_register function. The

Address this rename:

	Documentation/devicetree/bindings/sound/{sun4i-i2s.txt -> allwinner,sun4i-a10-i2s.yaml}

From d8481155a3219ef427c6384022931758fbbe8ebe Mon Sep 17 00:00:00 2001

Solves most of the pending broken references upstream, except for two of them:

	$ ./scripts/documentation-file-ref-check
	Documentation/riscv/boot-image-header.txt: Documentation/riscv/booting.txt
	MAINTAINERS: Documentation/devicetree/bindings/rng/samsung,exynos5250-trng.txt

As written at boot-image-header.txt, it is waiting for the addition of a future file:

"The complete booting guide will be available at
Documentation/riscv/booting.txt."

The second is due to this patch, pending to be merged:

	https://lore.kernel.org/patchwork/patch/994210/

I'm not a DT expert, but I can't see any issue with this patch, except for a missing acked-by a DT maintainer, and a possible conversion to yaml. IMO, the best fix for this would be to merge the DT patch.

Patch 1 was already submitted before, together with the v1 of my PDF fix series.

Mauro Carvalho Chehab (7):
docs: fix broken doc references due to renames
docs: generic-counter.rst: fix broken references for ABI file
MAINTAINERS: fix reference to net phy ABI file
MAINTAINERS: fix a renamed DT reference
docs: cgroup-v1/blkio-controller.rst: remove a CFQ left over
docs: zh_CN: howto.rst: fix a broken reference
docs: dt: fix a sound binding broken reference

  Documentation/RCU/rculist_nulls.txt                |  2 +-
  .../admin-guide/cgroup-v1/blkio-controller.rst     |  6 ------
  .../devicetree/bindings/arm/idle-states.txt        |  2 +-
  .../devicetree/bindings/sound/sun8i-a33-codec.txt  |  2 +-
  Documentation/driver-api/generic-counter.rst       |  4 ++--
  Documentation/locking/spinlocks.rst                |  4 ++--
  Documentation/memory-barriers.txt                  |  2 +-
  .../translations/ko_KR/memory-barriers.txt         |  2 +-
  Documentation/translations/zh_CN/process/howto.rst |  2 +-
  Documentation/watchdog/hpwdt.rst                   |  2 +-
  MAINTAINERS                                        | 14 +++++++-------
  drivers/gpu/drm/drm_modes.c                        |  2 +-
  drivers/i2c/busses/i2c-nvidia-gpu.c                |  2 +-
  drivers/scsi/hpsa.c                                |  4 ++--
  14 files changed, 22 insertions(+), 28 deletions(-)

Quoted 7 lines

Solves most of the pending broken references upstream, except for two of them:

	$ ./scripts/documentation-file-ref-check
	Documentation/riscv/boot-image-header.txt: Documentation/riscv/booting.txt
	MAINTAINERS: Documentation/devicetree/bindings/rng/samsung,exynos5250-trng.txt

Quoted 6 lines

As written at boot-image-header.txt, it is waiting for the addition of a future file:

"The complete booting guide will be available at
Documentation/riscv/booting.txt."

Yeah. We don't have complete booting guide defined in RISC-V land. Documentation/riscv/booting.txt will be available once we have that.

In the mean time, do we need to convert boot-image-header.txt to boot-image-header.rst and fix the reference to Documentation/riscv/booting.rst as well ?

Em Fri, 26 Jul 2019 12:55:36 -0700
Atish Patra <[email protected]> escreveu:

Quoted 15 lines · Mauro Carvalho Chehab

Quoted 7 lines

Solves most of the pending broken references upstream, except for two of them:

	$ ./scripts/documentation-file-ref-check
	Documentation/riscv/boot-image-header.txt: Documentation/riscv/booting.txt
	MAINTAINERS: Documentation/devicetree/bindings/rng/samsung,exynos5250-trng.txt

Quoted 6 lines

As written at boot-image-header.txt, it is waiting for the addition of a future file:

"The complete booting guide will be available at
Documentation/riscv/booting.txt."

Quoted 6 lines

Yeah. We don't have complete booting guide defined in RISC-V land. Documentation/riscv/booting.txt will be available once we have that.

In the mean time, do we need to convert boot-image-header.txt to boot-image-header.rst and fix the reference to Documentation/riscv/booting.rst as well ?

Well, in the mean time, every time someone builds the Kernel with COMPILE_TEST enabled, a warning will be produced.

So, my suggestion would be to write it on a different way, like:

"A complete booting guide is being written and should be
available on future versions."

Or:
TODO:
Write a complete booting guide.

And update this once the guide is finished. This should be enough to prevent the warning.

With regards to converting it to ReST, that's recommended. I suspect we could be able to finish the entire doc conversion in a couple Kernel versions.

Also, it should be really trivial to convert this one to ReST.

Thanks,
Mauro

Quoted 33 lines

Em Fri, 26 Jul 2019 12:55:36 -0700
Atish Patra <[email protected]> escreveu:

Quoted 15 lines · Mauro Carvalho Chehab

Quoted 7 lines

Solves most of the pending broken references upstream, except for two of them:

	$ ./scripts/documentation-file-ref-check
	Documentation/riscv/boot-image-header.txt: Documentation/riscv/booting.txt
	MAINTAINERS: Documentation/devicetree/bindings/rng/samsung,exynos5250-trng.txt

Quoted 6 lines

As written at boot-image-header.txt, it is waiting for the addition of a future file:

"The complete booting guide will be available at
Documentation/riscv/booting.txt."

Quoted 6 lines

Yeah. We don't have complete booting guide defined in RISC-V land. Documentation/riscv/booting.txt will be available once we have that.

In the mean time, do we need to convert boot-image-header.txt to boot-image-header.rst and fix the reference to Documentation/riscv/booting.rst as well ?

Well, in the mean time, every time someone builds the Kernel with COMPILE_TEST enabled, a warning will be produced.

So, my suggestion would be to write it on a different way, like:

"A complete booting guide is being written and should be
available on future versions."

Quoted 7 lines

Or:
TODO:
Write a complete booting guide.

And update this once the guide is finished. This should be enough to prevent the warning.

Sounds good to me.

Quoted 4 lines

With regards to converting it to ReST, that's recommended. I suspect we could be able to finish the entire doc conversion in a couple Kernel versions.

Sure.

Quoted 2 lines

Also, it should be really trivial to convert this one to ReST.

Yes. Let me know if you prefer to update it along with your series or I will send the patch.

Em Fri, 26 Jul 2019 13:18:30 -0700
Atish Patra <[email protected]> escreveu:

Quoted 50 lines · Mauro Carvalho Chehab

Quoted 33 lines

Em Fri, 26 Jul 2019 12:55:36 -0700
Atish Patra <[email protected]> escreveu:

Quoted 15 lines · Mauro Carvalho Chehab

Quoted 7 lines

Solves most of the pending broken references upstream, except for two of them:

	$ ./scripts/documentation-file-ref-check
	Documentation/riscv/boot-image-header.txt: Documentation/riscv/booting.txt
	MAINTAINERS: Documentation/devicetree/bindings/rng/samsung,exynos5250-trng.txt

Quoted 6 lines

As written at boot-image-header.txt, it is waiting for the addition of a future file:

"The complete booting guide will be available at
Documentation/riscv/booting.txt."

Quoted 6 lines

Yeah. We don't have complete booting guide defined in RISC-V land. Documentation/riscv/booting.txt will be available once we have that.

In the mean time, do we need to convert boot-image-header.txt to boot-image-header.rst and fix the reference to Documentation/riscv/booting.rst as well ?

Well, in the mean time, every time someone builds the Kernel with COMPILE_TEST enabled, a warning will be produced.

So, my suggestion would be to write it on a different way, like:

"A complete booting guide is being written and should be
available on future versions."

Quoted 7 lines

Or:
TODO:
Write a complete booting guide.

And update this once the guide is finished. This should be enough to prevent the warning.

Sounds good to me.

Quoted 4 lines

With regards to converting it to ReST, that's recommended. I suspect we could be able to finish the entire doc conversion in a couple Kernel versions.

Sure.

Quoted 5 lines

Quoted 2 lines

Also, it should be really trivial to convert this one to ReST.

Yes. Let me know if you prefer to update it along with your series or I will send the patch.

I suspect it would be quicker if I write it. I'm sending it in a few.

Thanks,
Mauro

Convert this small file to ReST format by:
- Using a proper markup for the document title;
- marking a code block as such;
- use tags for Author and date;
- use tables for bit map fields.

While here, fix a broken reference for a document with is planned but is not here yet.

Signed-off-by Mauro Carvalho Chehab <[email protected]>

---
  ...image-header.txt => boot-image-header.rst} | 39 ++++++++++++-------
  Documentation/riscv/index.rst                 |  1 +
  2 files changed, 26 insertions(+), 14 deletions(-)

rename Documentation/riscv/{boot-image-header.txt => boot-image-header.rst} (72%)

Documentation/riscv/boot-image-header.rst renamed from Documentation/riscv/boot-image-header.txt +25 -14

similarity index 72%
rename from Documentation/riscv/boot-image-header.txt
rename to Documentation/riscv/boot-image-header.rst
index 1b73fea23b39..43e9bd0731d5 100644
@@ -1,22 +1,25 @@
-				Boot image header in RISC-V Linux
-			=============================================
+=================================
+Boot image header in RISC-V Linux
+=================================
 
-Author: Atish Patra <[email protected]>
-Date  : 20 May 2019
+:Author: Atish Patra <[email protected]>
+:Date:   20 May 2019
 
  This document only describes the boot image header details for RISC-V Linux.
-The complete booting guide will be available at Documentation/riscv/booting.txt.
 
-The following 64-byte header is present in decompressed Linux kernel image.
+TODO:
+  Write a complete booting guide.
+
+The following 64-byte header is present in decompressed Linux kernel image::
 
  	u32 code0;		  /* Executable code */
-	u32 code1; 		  /* Executable code */
+	u32 code1;		  /* Executable code */
  	u64 text_offset;	  /* Image load offset, little endian */
  	u64 image_size;		  /* Effective Image size, little endian */
  	u64 flags;		  /* kernel flags, little endian */
  	u32 version;		  /* Version of this header */
-	u32 res1  = 0;		  /* Reserved */
-	u64 res2  = 0;    	  /* Reserved */
+	u32 res1 = 0;		  /* Reserved */
+	u64 res2 = 0;		  /* Reserved */
  	u64 magic = 0x5643534952; /* Magic number, little endian, "RISCV" */
  	u32 res3;		  /* Reserved for additional RISC-V specific header */
  	u32 res4;		  /* Reserved for PE COFF offset */

@@ -25,16 +28,21 @@ This header format is compliant with PE/COFF header and largely inspired from
  ARM64 header. Thus, both ARM64 & RISC-V header can be combined into one common
  header in future.
 
-Notes:
+Notes
+=====
+
  - This header can also be reused to support EFI stub for RISC-V in future. EFI
    specification needs PE/COFF image header in the beginning of the kernel image
    in order to load it as an EFI application. In order to support EFI stub,
    code0 should be replaced with "MZ" magic string and res5(at offset 0x3c) should
    point to the rest of the PE/COFF header.
 
-- version field indicate header version number.
-	Bits 0:15  - Minor version
-	Bits 16:31 - Major version
+- version field indicate header version number
+
+	==========  =============
+	Bits 0:15   Minor version
+	Bits 16:31  Major version
+	==========  =============
 
    This preserves compatibility across newer and older version of the header.
    The current version is defined as 0.1.

@@ -44,7 +52,10 @@ Notes:
    extension for RISC-V in future. For current version, it is set to be zero.
 
  - In current header, the flag field has only one field.
-	Bit 0: Kernel endianness. 1 if BE, 0 if LE.
+
+	=====  ====================================
+	Bit 0  Kernel endianness. 1 if BE, 0 if LE.
+	=====  ====================================
 
  - Image size is mandatory for boot loader to load kernel image. Booting will
    fail otherwise.

Documentation/riscv/index.rst +0 -0

index e3ca0922a8c2..215fd3c1f2d5 100644

Convert this small file to ReST format by:
- Using a proper markup for the document title;
- marking a code block as such;
- use tags for Author and date;
- use tables for bit map fields.

While here, fix a broken reference for a document with is planned but is not here yet.

Signed-off-by Mauro Carvalho Chehab <[email protected]>

Solves most of the pending broken references upstream, except for two of them:

	$ ./scripts/documentation-file-ref-check 
	Documentation/riscv/boot-image-header.txt: Documentation/riscv/booting.txt
	MAINTAINERS: Documentation/devicetree/bindings/rng/samsung,exynos5250-trng.txt

As written at boot-image-header.txt, it is waiting for the addition of a future file:

"The complete booting guide will be available at
Documentation/riscv/booting.txt."

The second is due to this patch, pending to be merged:

	https://lore.kernel.org/patchwork/patch/994210/

I'm not a DT expert, but I can't see any issue with this patch, except for a missing acked-by a DT maintainer, and a possible conversion to yaml. IMO, the best fix for this would be to merge the DT patch.

Patch 1 was already submitted before, together with the v1 of my PDF fix series.

Mauro Carvalho Chehab (7):
docs: fix broken doc references due to renames
docs: generic-counter.rst: fix broken references for ABI file
MAINTAINERS: fix reference to net phy ABI file
MAINTAINERS: fix a renamed DT reference
docs: cgroup-v1/blkio-controller.rst: remove a CFQ left over
docs: zh_CN: howto.rst: fix a broken reference
docs: dt: fix a sound binding broken reference

 Documentation/RCU/rculist_nulls.txt                |  2 +-
 .../admin-guide/cgroup-v1/blkio-controller.rst     |  6 ------
 .../devicetree/bindings/arm/idle-states.txt        |  2 +-
 .../devicetree/bindings/sound/sun8i-a33-codec.txt  |  2 +-
 Documentation/driver-api/generic-counter.rst       |  4 ++--
 Documentation/locking/spinlocks.rst                |  4 ++--
 Documentation/memory-barriers.txt                  |  2 +-
 .../translations/ko_KR/memory-barriers.txt         |  2 +-
 Documentation/translations/zh_CN/process/howto.rst |  2 +-
 Documentation/watchdog/hpwdt.rst                   |  2 +-
 MAINTAINERS                                        | 14 +++++++-------
 drivers/gpu/drm/drm_modes.c                        |  2 +-
 drivers/i2c/busses/i2c-nvidia-gpu.c                |  2 +-
 drivers/scsi/hpsa.c                                |  4 ++--
 14 files changed, 22 insertions(+), 28 deletions(-)