Commit 0ac624f4 authored by Mauro Carvalho Chehab's avatar Mauro Carvalho Chehab Committed by Jonathan Corbet

docs: fix some broken references

There are a number of documentation files that got moved or
renamed. update their references.
Signed-off-by: default avatarMauro Carvalho Chehab <mchehab+samsung@kernel.org>
Acked-by: default avatarShannon Nelson <snelson@pensando.io>
Acked-by: default avatarGuenter Roeck <linux@roeck-us.net>
Acked-by: default avatarRob Herring <robh@kernel.org>
Acked-by: Paul Walmsley <paul.walmsley@sifive.com> # RISC-V
Acked-by: default avatarBartosz Golaszewski <bgolaszewski@baylibre.com>
Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
parent 7f70ae56
...@@ -549,5 +549,5 @@ Example 3: HiFive Unleashed (RISC-V 64 bit, 4 core system) ...@@ -549,5 +549,5 @@ Example 3: HiFive Unleashed (RISC-V 64 bit, 4 core system)
[2] Devicetree NUMA binding description [2] Devicetree NUMA binding description
Documentation/devicetree/bindings/numa.txt Documentation/devicetree/bindings/numa.txt
[3] RISC-V Linux kernel documentation [3] RISC-V Linux kernel documentation
Documentation/devicetree/bindings/riscv/cpus.txt Documentation/devicetree/bindings/riscv/cpus.yaml
[4] https://www.devicetree.org/specifications/ [4] https://www.devicetree.org/specifications/
...@@ -2,7 +2,7 @@ Ingenic JZ47xx SoCs Timer/Counter Unit devicetree bindings ...@@ -2,7 +2,7 @@ Ingenic JZ47xx SoCs Timer/Counter Unit devicetree bindings
========================================================== ==========================================================
For a description of the TCU hardware and drivers, have a look at For a description of the TCU hardware and drivers, have a look at
Documentation/mips/ingenic-tcu.txt. Documentation/mips/ingenic-tcu.rst.
Required properties: Required properties:
......
...@@ -493,7 +493,7 @@ available but we try to move away from this: ...@@ -493,7 +493,7 @@ available but we try to move away from this:
gpiochip. It will pass the struct gpio_chip* for the chip to all IRQ gpiochip. It will pass the struct gpio_chip* for the chip to all IRQ
callbacks, so the callbacks need to embed the gpio_chip in its state callbacks, so the callbacks need to embed the gpio_chip in its state
container and obtain a pointer to the container using container_of(). container and obtain a pointer to the container using container_of().
(See Documentation/driver-model/design-patterns.txt) (See Documentation/driver-api/driver-model/design-patterns.rst)
- gpiochip_irqchip_add_nested(): adds a nested cascaded irqchip to a gpiochip, - gpiochip_irqchip_add_nested(): adds a nested cascaded irqchip to a gpiochip,
as discussed above regarding different types of cascaded irqchips. The as discussed above regarding different types of cascaded irqchips. The
......
...@@ -17,7 +17,7 @@ Usage Notes ...@@ -17,7 +17,7 @@ Usage Notes
----------- -----------
This driver does not auto-detect devices. You will have to instantiate the This driver does not auto-detect devices. You will have to instantiate the
devices explicitly. Please see Documentation/i2c/instantiating-devices for devices explicitly. Please see Documentation/i2c/instantiating-devices.rst for
details. details.
Sysfs entries Sysfs entries
......
...@@ -68,4 +68,4 @@ and frameworks can be controlled from the same registers, all of these ...@@ -68,4 +68,4 @@ and frameworks can be controlled from the same registers, all of these
drivers access their registers through the same regmap. drivers access their registers through the same regmap.
For more information regarding the devicetree bindings of the TCU drivers, For more information regarding the devicetree bindings of the TCU drivers,
have a look at Documentation/devicetree/bindings/mfd/ingenic,tcu.txt. have a look at Documentation/devicetree/bindings/timer/ingenic,tcu.txt.
...@@ -258,7 +258,7 @@ mlx5 tracepoints ...@@ -258,7 +258,7 @@ mlx5 tracepoints
================ ================
mlx5 driver provides internal trace points for tracking and debugging using mlx5 driver provides internal trace points for tracking and debugging using
kernel tracepoints interfaces (refer to Documentation/trace/ftrase.rst). kernel tracepoints interfaces (refer to Documentation/trace/ftrace.rst).
For the list of support mlx5 events check /sys/kernel/debug/tracing/events/mlx5/ For the list of support mlx5 events check /sys/kernel/debug/tracing/events/mlx5/
......
...@@ -3683,7 +3683,7 @@ M: Oleksij Rempel <o.rempel@pengutronix.de> ...@@ -3683,7 +3683,7 @@ M: Oleksij Rempel <o.rempel@pengutronix.de>
R: Pengutronix Kernel Team <kernel@pengutronix.de> R: Pengutronix Kernel Team <kernel@pengutronix.de>
L: linux-can@vger.kernel.org L: linux-can@vger.kernel.org
S: Maintained S: Maintained
F: Documentation/networking/j1939.txt F: Documentation/networking/j1939.rst
F: net/can/j1939/ F: net/can/j1939/
F: include/uapi/linux/can/j1939.h F: include/uapi/linux/can/j1939.h
......
...@@ -1835,7 +1835,7 @@ static int ftgmac100_probe(struct platform_device *pdev) ...@@ -1835,7 +1835,7 @@ static int ftgmac100_probe(struct platform_device *pdev)
} }
/* Indicate that we support PAUSE frames (see comment in /* Indicate that we support PAUSE frames (see comment in
* Documentation/networking/phy.txt) * Documentation/networking/phy.rst)
*/ */
phy_support_asym_pause(phy); phy_support_asym_pause(phy);
......
...@@ -596,8 +596,8 @@ enum ionic_txq_desc_opcode { ...@@ -596,8 +596,8 @@ enum ionic_txq_desc_opcode {
* the @encap is set, the device will * the @encap is set, the device will
* offload the outer header checksums using * offload the outer header checksums using
* LCO (local checksum offload) (see * LCO (local checksum offload) (see
* Documentation/networking/checksum- * Documentation/networking/checksum-offloads.rst
* offloads.txt for more info). * for more info).
* *
* IONIC_TXQ_DESC_OPCODE_CSUM_HW: * IONIC_TXQ_DESC_OPCODE_CSUM_HW:
* *
......
...@@ -1529,7 +1529,7 @@ init_cifs(void) ...@@ -1529,7 +1529,7 @@ init_cifs(void)
/* /*
* Consider in future setting limit!=0 maybe to min(num_of_cores - 1, 3) * Consider in future setting limit!=0 maybe to min(num_of_cores - 1, 3)
* so that we don't launch too many worker threads but * so that we don't launch too many worker threads but
* Documentation/workqueue.txt recommends setting it to 0 * Documentation/core-api/workqueue.rst recommends setting it to 0
*/ */
/* WQ_UNBOUND allows decrypt tasks to run on any CPU */ /* WQ_UNBOUND allows decrypt tasks to run on any CPU */
......
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