From: Michael Tretter <m.tretter@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Michael Tretter <m.tretter@pengutronix.de>
Subject: [PATCH 2/2] Documentation: blspec: drop documentation of devicetree-overlay
Date: Fri, 6 Mar 2020 15:37:32 +0100 [thread overview]
Message-ID: <20200306143732.24239-3-m.tretter@pengutronix.de> (raw)
In-Reply-To: <20200306143732.24239-1-m.tretter@pengutronix.de>
The devicetree-overlay key is part of the official Boot Loader
Specification. There is no need to document it in Barebox, again.
Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
---
Documentation/user/booting-linux.rst | 4 ----
1 file changed, 4 deletions(-)
diff --git a/Documentation/user/booting-linux.rst b/Documentation/user/booting-linux.rst
index 4b0ead1db5a5..983b56deefb6 100644
--- a/Documentation/user/booting-linux.rst
+++ b/Documentation/user/booting-linux.rst
@@ -232,10 +232,6 @@ device where the entry is found on. This makes it possible to use the same rootf
image on different devices without having to specify a different root= option each
time.
-Additionally to the options defined in the original spec, Barebox has the
-``devicetree-overlay`` option. This is a string value that refer to overlays
-that will be applied to the device tree before passing it to Linux.
-
Network boot
------------
--
2.20.1
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2020-03-06 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 14:37 [PATCH 0/2] Documentation: blspec: update documentation Michael Tretter
2020-03-06 14:37 ` [PATCH 1/2] Documentation: blspec: update link to Boot Loader Specification Michael Tretter
2020-03-06 14:37 ` Michael Tretter [this message]
2020-03-09 7:39 ` [PATCH 0/2] Documentation: blspec: update documentation Sascha Hauer
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=20200306143732.24239-3-m.tretter@pengutronix.de \
--to=m.tretter@pengutronix.de \
--cc=barebox@lists.infradead.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