From: Leif Lindholm <leif.lindholm@linaro.org>
To: Grant Likely <grant.likely@linaro.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, mark.rutland@arm.com,
robh+dt@kernel.org, plagnioj@jcrosoft.com, ijc@debian.org
Subject: Re: [PATCH] of: support passing console options with stdout-path
Date: Tue, 25 Nov 2014 15:15:16 +0000 [thread overview]
Message-ID: <20141125151515.GG2361@bivouac.eciton.net> (raw)
In-Reply-To: <20141125145854.A46EDC44343@trevor.secretlab.ca>
On Tue, Nov 25, 2014 at 02:58:54PM +0000, Grant Likely wrote:
> > + len = strchrnul(path, ':') - path;
> > +
> > for_each_property_of_node(of_aliases, pp) {
> > if (strlen(pp->name) == len && !strncmp(pp->name, path, len)) {
> > np = of_find_node_by_path(pp->value);
>
> Can you add a testcase to drivers/of/unittests.c for this new path
> parsing? Then we know it's correct!
Will do.
> > @@ -1830,8 +1835,12 @@ void of_alias_scan(void * (*dt_alloc)(u64 size, u64 align))
> > name = of_get_property(of_chosen, "linux,stdout-path", NULL);
> > if (IS_ENABLED(CONFIG_PPC) && !name)
> > name = of_get_property(of_aliases, "stdout", NULL);
> > - if (name)
> > + if (name) {
> > of_stdout = of_find_node_by_path(name);
> > + of_stdout_options = strchr(name, ':');
> > + if (of_stdout_options != NULL)
> > + of_stdout_options++;
> > + }
>
> Not so good. The ':' should actually be a generic part of
> of_find_node_by_path(), it doesn't have to be limited to stdout parsing.
> There are other places that would use it. I would add a second,
> optional, argument to of_find_node_by_path() that will update a pointer
> to the arguments after the ':'.
So, I agree this would be nicer...
However, I'm counting 157 callers of this function outside of
drivers/of and 43 inside. Any chance you'd let me get away with a
separate of_find_extra_options_by_path()?
/
Leif
next prev parent reply other threads:[~2014-11-25 15:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 22:23 Leif Lindholm
2014-11-24 23:00 ` Andrew Lunn
2014-11-25 0:12 ` Leif Lindholm
2014-11-25 6:49 ` Sascha Hauer
2014-11-25 14:44 ` Grant Likely
2014-11-25 16:21 ` Andrew Lunn
2014-11-25 10:35 ` Mark Rutland
2014-11-25 11:17 ` Leif Lindholm
2014-11-25 12:07 ` Ian Campbell
2014-11-25 14:35 ` Leif Lindholm
2014-11-25 14:55 ` Grant Likely
2014-11-25 12:54 ` Sascha Hauer
2014-11-25 14:58 ` Grant Likely
2014-11-25 15:15 ` Leif Lindholm [this message]
2014-11-25 15:20 ` Grant Likely
2014-11-25 15:24 ` Ian Campbell
2014-11-25 15:39 ` Grant Likely
2014-11-25 15:41 ` Ian Campbell
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=20141125151515.GG2361@bivouac.eciton.net \
--to=leif.lindholm@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=ijc@debian.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=plagnioj@jcrosoft.com \
--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 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®