mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
	Rob Herring <robh+dt@kernel.org>,
	devicetree@vger.kernel.org
Subject: [PATCH v3 03/12] docs: dt: usage_model.rst: fix link for DT usage
Date: Wed, 15 Apr 2020 16:45:17 +0200	[thread overview]
Message-ID: <5af2521377cecc4b5f7cc9253600ff335c596ee2.1586961793.git.mchehab+huawei@kernel.org> (raw)
In-Reply-To: <cover.1586961793.git.mchehab+huawei@kernel.org>

The devicetree.org doesn't host the Device_Tree_Usage page
anymore. So, fix the link to point to a new address.

Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
---
 Documentation/devicetree/usage-model.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/devicetree/usage-model.rst b/Documentation/devicetree/usage-model.rst
index 326d7af10c5b..e1b42dc63f01 100644
--- a/Documentation/devicetree/usage-model.rst
+++ b/Documentation/devicetree/usage-model.rst
@@ -12,7 +12,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
 
 The "Open Firmware Device Tree", or simply Device Tree (DT), is a data
 structure and language for describing hardware.  More specifically, it
-- 
2.25.2


  parent reply	other threads:[~2020-04-15 14:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-15 14:45 [PATCH v3 00/12] Convert some DT documentation files to ReST Mauro Carvalho Chehab
2020-04-15 14:45 ` [PATCH v3 01/12] docs: dt: add an index.rst file for devicetree Mauro Carvalho Chehab
2020-04-15 14:45 ` [PATCH v3 02/12] docs: dt: convert usage-model.txt to ReST Mauro Carvalho Chehab
2020-04-16  6:28   ` Lee Jones
2020-04-15 14:45 ` Mauro Carvalho Chehab [this message]
2020-04-15 14:45 ` [PATCH v3 04/12] docs: dt: convert booting-without-of.txt to ReST format Mauro Carvalho Chehab
2020-04-15 14:45 ` [PATCH v3 05/12] docs: dt: convert changesets to ReST Mauro Carvalho Chehab
2020-04-15 14:45 ` [PATCH v3 06/12] docs: dt: convert dynamic-resolution-notes.txt " Mauro Carvalho Chehab
2020-04-15 14:45 ` [PATCH v3 07/12] docs: dt: convert of_unittest.txt " Mauro Carvalho Chehab
2020-04-15 14:45 ` [PATCH v3 08/12] docs: dt: convert overlay-notes.txt to ReST format Mauro Carvalho Chehab
2020-04-15 14:45 ` [PATCH v3 09/12] docs: dt: minor adjustments at writing-schema.rst Mauro Carvalho Chehab
2020-04-15 14:45 ` [PATCH v3 10/12] docs: dt: convert ABI.txt to ReST format Mauro Carvalho Chehab
2020-04-15 14:45 ` [PATCH v3 11/12] docs: dt: convert submitting-patches.txt " Mauro Carvalho Chehab
2020-04-15 14:45 ` [PATCH v3 12/12] docs: dt: convert writing-bindings.txt to ReST Mauro Carvalho Chehab
2020-05-05  3:38 ` [PATCH v3 00/12] Convert some DT documentation files " Rob Herring

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=5af2521377cecc4b5f7cc9253600ff335c596ee2.1586961793.git.mchehab+huawei@kernel.org \
    --to=mchehab+huawei@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@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®