linux-kernel - Re: [PATCH resend] Documentation: Update of broken link

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: <d2cf5c26-dac5-2e41-e2d3-a8eb8228af97@infradead.org>
Date:   Sun, 5 Nov 2017 09:00:07 -0800
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Jonathan Corbet <corbet@....net>,
        Claudia Meitinger <claudia.meitinger@...augsburg.de>
Cc:     linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH resend] Documentation: Update of broken link

On 11/05/2017 08:44 AM, Jonathan Corbet wrote:
> On Thu, 2 Nov 2017 06:26:18 +0100
> Claudia Meitinger <claudia.meitinger@...augsburg.de> wrote:
> 
>> The link of devicetree.org was broken. Site has
>> been moved to elinux.org.
>>
>> Signed-off-by: Claudia Meitinger <claudia.meitinger@...augsburg.de>
>> ---
>>  Documentation/devicetree/usage-model.txt | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/Documentation/devicetree/usage-model.txt
>> b/Documentation/devicetree/usage-model.txt
>> index 33a8aaac..d7248c2f 100644
>> --- a/Documentation/devicetree/usage-model.txt
>> +++ b/Documentation/devicetree/usage-model.txt
>> @@ -8,7 +8,7 @@ This article describes how Linux uses the device tree.
>> An overview of
>>  the device tree data format can be found on the device tree usage page
>>  at devicetree.org[1].
>>
>> -[1] http://devicetree.org/Device_Tree_Usage
>> +[1] https://elinux.org/Device_Tree_Usage
> 
> That link works just fine for me ... ?

The first link redirects to the second one for me, so IMO the second one
is the preferred link.

> If you really think that this change needs to be made, please submit the
> patch to the device tree maintainers; that area is not something that I
> maintain.


-- 
~Randy