mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Jonathan Corbet <corbet@lwn.net>,
	Claudia Meitinger <claudia.meitinger@hs-augsburg.de>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH resend] Documentation: Update of broken link
Date: Sun, 5 Nov 2017 09:00:07 -0800	[thread overview]
Message-ID: <d2cf5c26-dac5-2e41-e2d3-a8eb8228af97@infradead.org> (raw)
In-Reply-To: <20171105094439.7894b6d8@lwn.net>

On 11/05/2017 08:44 AM, Jonathan Corbet wrote:
> On Thu, 2 Nov 2017 06:26:18 +0100
> Claudia Meitinger <claudia.meitinger@hs-augsburg.de> wrote:
> 
>> The link of devicetree.org was broken. Site has
>> been moved to elinux.org.
>>
>> Signed-off-by: Claudia Meitinger <claudia.meitinger@hs-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

      reply	other threads:[~2017-11-05 17:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-24 18:03 [PATCH] " Claudia Meitinger
2017-11-02  5:26 ` [PATCH resend] " Claudia Meitinger
2017-11-05 16:44   ` Jonathan Corbet
2017-11-05 17:00     ` Randy Dunlap [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=d2cf5c26-dac5-2e41-e2d3-a8eb8228af97@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=claudia.meitinger@hs-augsburg.de \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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®