linux-kernel - Re: [PATCH] docs: arm: keystone: fix link to devicetree binding document

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <87pl86yx7f.fsf@trenco.lwn.net>
Date: Mon, 22 Dec 2025 15:21:24 -0700
From: Jonathan Corbet <corbet@....net>
To: Kathara Sasikumar <katharasasikumar007@...il.com>
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
 shuah@...nel.org, skhan@...uxfoundation.org, david.hunter.linux@...il.com,
 katharasasikumar007@...il.com
Subject: Re: [PATCH] docs: arm: keystone: fix link to devicetree binding
 document

Kathara Sasikumar <katharasasikumar007@...il.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@...il.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