From: "Milan Lakhani" <milan.lakhani@codethink.co.uk>
To: lukas.bulwahn@gmail.com, sudip.mukherjee@codethink.co.uk,
linux-safety@lists.elisa.tech, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, corbet@lwn.net, harryxiyou@gmail.com,
alex.shi@linux.alibaba.com
Cc: Milan Lakhani <milan.lakhani@codethink.co.uk>
Subject: [linux-safety] [PATCH] docs: Change reference that was to removed file
Date: Tue, 19 Jan 2021 10:26:20 +0000 [thread overview]
Message-ID: <1611051980-3834-1-git-send-email-milan.lakhani@codethink.co.uk> (raw)
There were two references to
Documentation/devicetree/booting-without-of.rst for dtb format
information. This file has been removed, so I have changed the links to
Documentation/devicetree/usage-model.rst for this information, which
itself points to https://elinux.org/Device_Tree_Usage for an overview of
the device tree data format.
Signed-off-by: Milan Lakhani <milan.lakhani@codethink.co.uk>
---
Documentation/arm/booting.rst | 2 +-
Documentation/translations/zh_CN/arm/Booting | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/arm/booting.rst b/Documentation/arm/booting.rst
index a226345..5392d01 100644
--- a/Documentation/arm/booting.rst
+++ b/Documentation/arm/booting.rst
@@ -128,7 +128,7 @@ it. The recommended placement is in the first 16KiB of RAM.
The boot loader must load a device tree image (dtb) into system ram
at a 64bit aligned address and initialize it with the boot data. The
-dtb format is documented in Documentation/devicetree/booting-without-of.rst.
+dtb format is documented in Documentation/devicetree/usage-model.rst.
The kernel will look for the dtb magic value of 0xd00dfeed at the dtb
physical address to determine if a dtb has been passed instead of a
tagged list.
diff --git a/Documentation/translations/zh_CN/arm/Booting b/Documentation/translations/zh_CN/arm/Booting
index c3d26ce..d2939c7 100644
--- a/Documentation/translations/zh_CN/arm/Booting
+++ b/Documentation/translations/zh_CN/arm/Booting
@@ -124,7 +124,7 @@ bootloader 必须传递一个系统内存的位置和最小值,以及根文件
bootloader 必须以 64bit 地址对齐的形式加载一个设备树映像(dtb)到系统
RAM 中,并用启动数据初始化它。dtb 格式在文档
-Documentation/devicetree/booting-without-of.rst 中。内核将会在
+Documentation/devicetree/usage-model.rst 中。内核将会在
dtb 物理地址处查找 dtb 魔数值(0xd00dfeed),以确定 dtb 是否已经代替
标签列表被传递进来。
--
2.7.4
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#232): https://lists.elisa.tech/g/linux-safety/message/232
Mute This Topic: https://lists.elisa.tech/mt/79948363/5278000
Group Owner: linux-safety+owner@lists.elisa.tech
Unsubscribe: https://lists.elisa.tech/g/linux-safety/unsub [linux-safety@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
next reply other threads:[~2021-01-19 10:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 10:26 Milan Lakhani [this message]
2021-01-20 0:01 ` [linux-safety] [PATCH] docs: Change reference that was to removed file Jonathan Corbet
2021-01-20 1:07 ` Rob Herring
2021-01-20 14:46 ` Milan Lakhani
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=1611051980-3834-1-git-send-email-milan.lakhani@codethink.co.uk \
--to=milan.lakhani@codethink.co.uk \
--cc=alex.shi@linux.alibaba.com \
--cc=corbet@lwn.net \
--cc=harryxiyou@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-safety@lists.elisa.tech \
--cc=lukas.bulwahn@gmail.com \
--cc=sudip.mukherjee@codethink.co.uk \
/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;
as well as URLs for NNTP newsgroup(s).