Commit bff9e34c authored by Mauro Carvalho Chehab's avatar Mauro Carvalho Chehab

docs: fix broken doc references due to renames

Some files got renamed but probably due to some merge conflicts,
a few references still point to the old locations.
Signed-off-by: default avatarMauro Carvalho Chehab <mchehab+samsung@kernel.org>
parent 08a69058
Using hlist_nulls to protect read-mostly linked lists and Using hlist_nulls to protect read-mostly linked lists and
objects using SLAB_TYPESAFE_BY_RCU allocations. 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 Using special makers (called 'nulls') is a convenient way
to solve following problem : to solve following problem :
......
...@@ -703,4 +703,4 @@ cpus { ...@@ -703,4 +703,4 @@ cpus {
https://www.devicetree.org/specifications/ https://www.devicetree.org/specifications/
[6] ARM Linux Kernel documentation - Booting AArch64 Linux [6] ARM Linux Kernel documentation - Booting AArch64 Linux
Documentation/arm64/booting.txt Documentation/arm64/booting.rst
...@@ -82,7 +82,7 @@ itself. The read lock allows many concurrent readers. Anything that ...@@ -82,7 +82,7 @@ itself. The read lock allows many concurrent readers. Anything that
**changes** the list will have to get the write lock. **changes** the list will have to get the write lock.
NOTE! RCU is better for list traversal, but requires careful 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_ 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 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. ...@@ -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 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 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.)
---- ----
......
...@@ -548,7 +548,7 @@ There are certain things that the Linux kernel memory barriers do not guarantee: ...@@ -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: [*] 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-HOWTO.txt
Documentation/DMA-API.txt Documentation/DMA-API.txt
......
...@@ -569,7 +569,7 @@ ACQUIRE 는 해당 오퍼레이션의 로드 부분에만 적용되고 RELEASE ...@@ -569,7 +569,7 @@ ACQUIRE 는 해당 오퍼레이션의 로드 부분에만 적용되고 RELEASE
[*] 버스 마스터링 DMA 와 일관성에 대해서는 다음을 참고하시기 바랍니다: [*] 버스 마스터링 DMA 와 일관성에 대해서는 다음을 참고하시기 바랍니다:
Documentation/PCI/pci.rst Documentation/driver-api/pci/pci.rst
Documentation/DMA-API-HOWTO.txt Documentation/DMA-API-HOWTO.txt
Documentation/DMA-API.txt Documentation/DMA-API.txt
......
...@@ -59,7 +59,7 @@ Last reviewed: 08/20/2018 ...@@ -59,7 +59,7 @@ Last reviewed: 08/20/2018
and loop forever. This is generally not what a watchdog user wants. and loop forever. This is generally not what a watchdog user wants.
For those wishing to learn more please see: 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=) Documentation/admin-guide/kernel-parameters.txt (panic=)
Your Linux Distribution specific documentation. Your Linux Distribution specific documentation.
......
...@@ -899,7 +899,7 @@ L: linux-iio@vger.kernel.org ...@@ -899,7 +899,7 @@ L: linux-iio@vger.kernel.org
W: http://ez.analog.com/community/linux-device-drivers W: http://ez.analog.com/community/linux-device-drivers
S: Supported S: Supported
F: drivers/iio/adc/ad7124.c 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 ANALOG DEVICES INC AD7606 DRIVER
M: Stefan Popa <stefan.popa@analog.com> M: Stefan Popa <stefan.popa@analog.com>
...@@ -4189,7 +4189,7 @@ M: Jens Axboe <axboe@kernel.dk> ...@@ -4189,7 +4189,7 @@ M: Jens Axboe <axboe@kernel.dk>
L: cgroups@vger.kernel.org L: cgroups@vger.kernel.org
L: linux-block@vger.kernel.org L: linux-block@vger.kernel.org
T: git git://git.kernel.dk/linux-block 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: block/blk-cgroup.c
F: include/linux/blk-cgroup.h F: include/linux/blk-cgroup.h
F: block/blk-throttle.c F: block/blk-throttle.c
...@@ -6848,7 +6848,7 @@ R: Sagi Shahar <sagis@google.com> ...@@ -6848,7 +6848,7 @@ R: Sagi Shahar <sagis@google.com>
R: Jon Olson <jonolson@google.com> R: Jon Olson <jonolson@google.com>
L: netdev@vger.kernel.org L: netdev@vger.kernel.org
S: Supported S: Supported
F: Documentation/networking/device_drivers/google/gve.txt F: Documentation/networking/device_drivers/google/gve.rst
F: drivers/net/ethernet/google F: drivers/net/ethernet/google
GPD POCKET FAN DRIVER GPD POCKET FAN DRIVER
...@@ -12096,7 +12096,7 @@ M: Juergen Gross <jgross@suse.com> ...@@ -12096,7 +12096,7 @@ M: Juergen Gross <jgross@suse.com>
M: Alok Kataria <akataria@vmware.com> M: Alok Kataria <akataria@vmware.com>
L: virtualization@lists.linux-foundation.org L: virtualization@lists.linux-foundation.org
S: Supported S: Supported
F: Documentation/virtual/paravirt_ops.txt F: Documentation/virtual/paravirt_ops.rst
F: arch/*/kernel/paravirt* F: arch/*/kernel/paravirt*
F: arch/*/include/asm/paravirt*.h F: arch/*/include/asm/paravirt*.h
F: include/linux/hypervisor.h F: include/linux/hypervisor.h
......
...@@ -1680,7 +1680,7 @@ static int drm_mode_parse_cmdline_options(char *str, size_t len, ...@@ -1680,7 +1680,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 * Additionals options can be provided following the mode, using a comma to
* separate each option. Valid options can be found in * 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 * The intermediate drm_cmdline_mode structure is required to store additional
* options from the command line modline like the force-enable/disable flag. * options from the command line modline like the force-enable/disable flag.
......
...@@ -364,7 +364,7 @@ static void gpu_i2c_remove(struct pci_dev *pdev) ...@@ -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 * 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. * 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) static __maybe_unused int gpu_i2c_suspend(struct device *dev)
{ {
......
...@@ -7798,7 +7798,7 @@ static void hpsa_free_pci_init(struct ctlr_info *h) ...@@ -7798,7 +7798,7 @@ static void hpsa_free_pci_init(struct ctlr_info *h)
hpsa_disable_interrupt_mode(h); /* pci_init 2 */ hpsa_disable_interrupt_mode(h); /* pci_init 2 */
/* /*
* call pci_disable_device before pci_release_regions per * 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_disable_device(h->pdev); /* pci_init 1 */
pci_release_regions(h->pdev); /* pci_init 2 */ pci_release_regions(h->pdev); /* pci_init 2 */
...@@ -7881,7 +7881,7 @@ static int hpsa_pci_init(struct ctlr_info *h) ...@@ -7881,7 +7881,7 @@ static int hpsa_pci_init(struct ctlr_info *h)
clean1: clean1:
/* /*
* call pci_disable_device before pci_release_regions per * 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_disable_device(h->pdev);
pci_release_regions(h->pdev); pci_release_regions(h->pdev);
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment