@@ -4,7 +4,8 @@ This controller is present on BCM6318, BCM6328, BCM6362 and BCM63268. In these SoCs it's possible to control LEDs both as GPIOs or by hardware. However, on some devices there are Serial LEDs (LEDs connected to a 74x164 controller), which can either be controlled by software (exporting the 74x164-as spi-gpio. See Documentation/devicetree/bindings/gpio/gpio-74x164.txt), or+as spi-gpio; see+Documentation/devicetree/bindings/gpio/fairchild,74hc595.yaml), or by hardware using this driver. Some of these Serial LEDs are hardware controlled (e.g. ethernet LEDs) and exporting the 74x164 as spi-gpio prevents those LEDs to be hardware
@@ -2,8 +2,8 @@ LEDs connected to Broadcom BCM6358 controller This controller is present on BCM6358 and BCM6368. In these SoCs there are Serial LEDs (LEDs connected to a 74x164 controller),-which can either be controlled by software (exporting the 74x164 as spi-gpio.-See Documentation/devicetree/bindings/gpio/gpio-74x164.txt), or+which can either be controlled by software (exporting the 74x164 as spi-gpio;+see Documentation/devicetree/bindings/gpio/fairchild,74hc595.yaml), or by hardware using this driver. Required properties:
@@ -392,7 +392,7 @@ When mounting an ext4 filesystem, the following option are accepted: dax Use direct access (no page cache). See- Documentation/filesystems/dax.txt. Note that this option is+ Documentation/filesystems/dax.rst. Note that this option is incompatible with data=journal. inlinecrypt
@@ -25,7 +25,7 @@ check=none, nocheck (*) Don't do extra checking of bitmaps on mount (check=normal and check=strict options removed) dax Use direct access (no page cache). See- Documentation/filesystems/dax.txt.+ Documentation/filesystems/dax.rst. debug Extra debugging information is sent to the kernel syslog. Useful for developers.
From: Kir Kolyshkin <hidden> Date: 2021-06-11 03:02:23
Commits 3c5be0454 and ce49e4282 renamed the files being referenced,
but forgot to modify the document that references them.
This fixes the following warnings:
Warning: Documentation/devicetree/bindings/mfd/motorola-cpcap.txt
references a file that doesn't exist:
Documentation/devicetree/bindings/power/supply/cpcap-battery.txt
Warning: Documentation/devicetree/bindings/mfd/motorola-cpcap.txt
references a file that doesn't exist:
Documentation/devicetree/bindings/power/supply/cpcap-charger.txt
Cc: Sebastian Reichel <redacted>
Signed-off-by: Kir Kolyshkin <redacted>
---
Documentation/devicetree/bindings/mfd/motorola-cpcap.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
@@ -16,8 +16,8 @@ Optional subnodes: The sub-functions of CPCAP get their own node with their own compatible values, which are described in the following files:-- Documentation/devicetree/bindings/power/supply/cpcap-battery.txt-- Documentation/devicetree/bindings/power/supply/cpcap-charger.txt+- Documentation/devicetree/bindings/power/supply/cpcap-battery.yaml+- Documentation/devicetree/bindings/power/supply/cpcap-charger.yaml - Documentation/devicetree/bindings/regulator/cpcap-regulator.txt - Documentation/devicetree/bindings/phy/phy-cpcap-usb.txt - Documentation/devicetree/bindings/input/cpcap-pwrbutton.txt
Hi Kir,
On Fri, Jun 11, 2021 at 5:01 AM Kir Kolyshkin [off-list ref] wrote:
Commit 56b01acc1c79 renames the file being referred to.
Fix the references accordingly.
Cc: Geert Uytterhoeven <geert+renesas@glider.be>
Signed-off-by: Kir Kolyshkin <redacted>
Thanks for your patch, but this was already fixed in v5.13-rc3 in commit
0bd50826a40e012a ("leds: Fix reference file name of documentation").
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds