From: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: James Hogan <james.hogan@mips.com>,
Linux MIPS Mailing List <linux-mips@linux-mips.org>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] MIPS: implement a "bootargs-append" DT property
Date: Mon, 13 Nov 2017 04:42:33 -0800 [thread overview]
Message-ID: <1510576953.9806.1.camel@chimera> (raw)
In-Reply-To: <CAMuHMdUtHhSLbrgmOW7gkEUg8pif+Ddc-zZgWzCZ4WL3JTeOKg@mail.gmail.com>
On Mon, 2017-11-13 at 13:31 +0100, Geert Uytterhoeven wrote:
> I've seen other use cases, e.g. the extension of the du node's
> "clocks" and
> "clock-names" properties from arch/arm64/boot/dts/renesas/r8a7795.dtsi
> to
> arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts.
>
> To avoid the proliferation of "-append" versions of existing
> properties, what
> about handling this in dtc, by adding support for an
> "/append-property/"
> keyword?
That would not address use case #2 that I mentioned, where the dtb would
have a "bootargs-append" property but no "bootargs" property.
next prev parent reply other threads:[~2017-11-13 12:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-11 17:19 [PATCH] MIPS: implement a "bootargs-append" DT property Daniel Gimpelevich
2017-11-13 11:23 ` James Hogan
2017-11-13 11:23 ` James Hogan
2017-11-13 11:23 ` James Hogan
2017-11-13 12:31 ` Geert Uytterhoeven
2017-11-13 12:42 ` Daniel Gimpelevich [this message]
2017-11-13 13:18 ` Geert Uytterhoeven
2017-11-13 13:18 ` Geert Uytterhoeven
2017-11-13 16:34 ` Rob Herring
2017-11-13 16:34 ` Rob Herring
2017-11-14 3:05 ` Daniel Gimpelevich
2017-11-14 3:05 ` Daniel Gimpelevich
2017-11-14 17:18 ` Rob Herring
2017-11-14 17:18 ` Rob Herring
2017-11-16 1:46 ` Daniel Gimpelevich
2017-11-16 1:46 ` Daniel Gimpelevich
2017-11-16 5:26 ` 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=1510576953.9806.1.camel@chimera \
--to=daniel@gimpelevich.san-francisco.ca.us \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=geert@linux-m68k.org \
--cc=james.hogan@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=linux-renesas-soc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.