From: Rob Herring <robh@kernel.org>
To: Kir Kolyshkin <kolyshkin@gmail.com>
Cc: devicetree@vger.kernel.org, lee.jones@linaro.org,
Sebastian Reichel <sebastian.reichel@collabora.com>
Subject: Re: [PATCH] docs: fix bad cross-links in motorola-cpcap
Date: Thu, 24 Jun 2021 14:42:22 -0600 [thread overview]
Message-ID: <20210624204222.GA1953445@robh.at.kernel.org> (raw)
In-Reply-To: <20210614214527.208384-1-kolyshkin@gmail.com>
On Mon, Jun 14, 2021 at 02:45:27PM -0700, Kir Kolyshkin wrote:
> 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(-)
There's already fixes for this in linux-next.
>
> 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
>
>
prev parent reply other threads:[~2021-06-24 20:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 21:45 [PATCH] docs: fix bad cross-links in motorola-cpcap Kir Kolyshkin
2021-06-24 20:42 ` Rob Herring [this message]
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=20210624204222.GA1953445@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kolyshkin@gmail.com \
--cc=lee.jones@linaro.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).