From: "Baeuerle, Florian" <Florian.Baeuerle@allegion.com>
To: "s.hauer@pengutronix.de" <s.hauer@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: Modifying device-tree: /chosen
Date: Thu, 24 May 2018 14:12:20 +0000 [thread overview]
Message-ID: <6fc771578dc59b189cebf73a3a9510042fce0c60.camel@allegion.com> (raw)
In-Reply-To: <20180524082047.44njsmnrvpxyar27@pengutronix.de>
Hi Sascha,
Am Donnerstag, den 24.05.2018, 10:20 +0200 schrieb s.hauer@pengutronix.de:
> On Thu, May 24, 2018 at 08:13:44AM +0000, Baeuerle, Florian wrote:
> > Hi Sascha,
> >
> > so I think we need a command, similar to of_property:
> >
> > of_fixup_property [-sd] NODE PROPERTY VALUE
> >
> > or should it rather be a new option for of_property, like this:
> >
> > of_property [-sdf] NODE [PROPERTY] [VALUES]
>
> I would first try it as a new option to of_property.
> If for some reason this turns out to be ugly, let me know.
of_property and of_node are pretty similar with regard to their options.
Do you want them to stay the same, so I'd also have to implement this
fixup functionality to of_node?
>
> Sascha
>
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2018-05-24 14:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 10:59 Baeuerle, Florian
2018-05-23 12:55 ` Pascal Vizeli
2018-05-23 13:30 ` Sascha Hauer
[not found] ` <e77f7ef6c9ab77ca5fb2cdee4125efa6c9ae8fd2.camel@allegion.com>
[not found] ` <20180524082047.44njsmnrvpxyar27@pengutronix.de>
2018-05-24 14:12 ` Baeuerle, Florian [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=6fc771578dc59b189cebf73a3a9510042fce0c60.camel@allegion.com \
--to=florian.baeuerle@allegion.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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