mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Kathara Sasikumar <katharasasikumar007@gmail.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	shuah@kernel.org, skhan@linuxfoundation.org,
	david.hunter.linux@gmail.com, katharasasikumar007@gmail.com
Subject: Re: [PATCH] docs: arm: keystone: fix link to devicetree binding document
Date: Mon, 22 Dec 2025 15:21:24 -0700	[thread overview]
Message-ID: <87pl86yx7f.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20251205174933.619122-1-katharasasikumar007@gmail.com>

Kathara Sasikumar <katharasasikumar007@gmail.com> writes:

> make refcheckdocs reports a broken link in the Keystone architecture
> overview. The referenced devicetree binding was converted from .txt to
> YAML schema and moved under arm/ti/. Updated the link to point to the
> current location.
>
> Signed-off-by: Kathara Sasikumar <katharasasikumar007@gmail.com>
> ---
>  Documentation/arch/arm/keystone/overview.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/arch/arm/keystone/overview.rst b/Documentation/arch/arm/keystone/overview.rst
> index cd90298c493c..bf791b2fc43f 100644
> --- a/Documentation/arch/arm/keystone/overview.rst
> +++ b/Documentation/arch/arm/keystone/overview.rst
> @@ -65,7 +65,7 @@ specified through DTS. Following are the DTS used:
>  
>  The device tree documentation for the keystone machines are located at
>  
> -        Documentation/devicetree/bindings/arm/keystone/keystone.txt
> +        Documentation/devicetree/bindings/arm/ti/ti,keystone.yaml

Thanks for this ... I applied another patch to the same effect only
because I stumbled across it first in my overflowing docs folder.
Otherwise this would have been fine.

Thanks,

jon

      reply	other threads:[~2025-12-22 22:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-05 17:49 Kathara Sasikumar
2025-12-22 22:21 ` Jonathan Corbet [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=87pl86yx7f.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=david.hunter.linux@gmail.com \
    --cc=katharasasikumar007@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=skhan@linuxfoundation.org \
    /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

all inboxes | Powered by JetHome®