From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: Rob Herring <robh@kernel.org>
Cc: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
devicetree@vger.kernel.org, "Mark Rutland" <mark.rutland@arm.com>,
"AKASHI Takahiro" <takahiro.akashi@linaro.org>,
"Ard Biesheuvel" <ard.biesheuvel@linaro.org>,
"Kees Cook" <keescook@chromium.org>,
"James Morse" <james.morse@arm.com>,
"Frank Rowand" <frank.rowand@sony.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: chosen: Document linux,initrd-{start,end}
Date: Sat, 16 Dec 2017 06:41:39 +0100 [thread overview]
Message-ID: <20171216054139.d6hkbasex3p7h3qo@latitude> (raw)
In-Reply-To: <20171215210147.w3xqs3di2vbbvv5p@rob-hp-laptop>
[-- Attachment #1: Type: text/plain, Size: 955 bytes --]
On Fri, Dec 15, 2017 at 03:01:47PM -0600, Rob Herring wrote:
> On Sat, Dec 09, 2017 at 04:33:02PM +0100, Jonathan Neuschäfer wrote:
> > These properties have been in use for a very long time (at least since
> > 2005), but were never documented in chosen.txt.
> >
> > Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
> > ---
> > Documentation/devicetree/bindings/chosen.txt | 15 +++++++++++++++
> > 1 file changed, 15 insertions(+)
>
> Applied.
Thanks.
> I'm inclined to say to document these in the DT spec, but I'm assuming
> there was some reason why they weren't put into the spec (ePAPR at the
> time) originally.
I don't know about the history of this, but I think if and when these
properties were specified in DTSpec, they should get a non-linux-specific
name, such as initrd-start/initrd-end, and a compatibility fallback to
linux,initrd-* (similar to stdout-path and phandle).
Jonathan Neuschäfer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2017-12-16 5:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-09 15:33 Jonathan Neuschäfer
2017-12-15 21:01 ` Rob Herring
2017-12-16 5:41 ` Jonathan Neuschäfer [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=20171216054139.d6hkbasex3p7h3qo@latitude \
--to=j.neuschaefer@gmx.net \
--cc=ard.biesheuvel@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=frank.rowand@sony.com \
--cc=james.morse@arm.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh@kernel.org \
--cc=takahiro.akashi@linaro.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®