linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kir Kolyshkin <kolyshkin@gmail.com>
To: linux-doc@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>,
	Kir Kolyshkin <kolyshkin@gmail.com>,
	Sebastian Reichel <sebastian.reichel@collabora.com>
Subject: [PATCH 1/3] docs: fix bad cross-links in motorola-cpcap
Date: Thu, 10 Jun 2021 20:00:42 -0700	[thread overview]
Message-ID: <20210611030044.1982911-2-kolyshkin@gmail.com> (raw)
In-Reply-To: <20210611030044.1982911-1-kolyshkin@gmail.com>

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 <sebastian.reichel@collabora.com>
Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
---
 Documentation/devicetree/bindings/mfd/motorola-cpcap.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/devicetree/bindings/mfd/motorola-cpcap.txt b/Documentation/devicetree/bindings/mfd/motorola-cpcap.txt
index b52e7a33f0f9..190230216de8 100644
--- a/Documentation/devicetree/bindings/mfd/motorola-cpcap.txt
+++ b/Documentation/devicetree/bindings/mfd/motorola-cpcap.txt
@@ -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
-- 
2.31.1


  reply	other threads:[~2021-06-11  3:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-11  3:00 [PATCH 0/3] docs: fix cross references Kir Kolyshkin
2021-06-11  3:00 ` Kir Kolyshkin [this message]
2021-06-11  3:00 ` [PATCH 2/3] docs/devicetree: fix a cross-ref Kir Kolyshkin
2021-06-11  6:57   ` Geert Uytterhoeven
2021-06-11  3:00 ` [PATCH 3/3] docs: " Kir Kolyshkin
2021-06-13 23:03   ` Jonathan Corbet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210611030044.1982911-2-kolyshkin@gmail.com \
    --to=kolyshkin@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=sebastian.reichel@collabora.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).