From: Grant Likely <grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Bryan Wu <cooloney-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Alexander Shiyan <shc_work-JGs/UdohzUI@public.gmane.org>
Cc: "devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org"
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
Linux LED Subsystem
<linux-leds-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>
Subject: Re: [PATCH] of: Add more stubs for non-OF builds
Date: Fri, 21 Jun 2013 01:26:07 +0100 [thread overview]
Message-ID: <20130621002607.F24A63E093E@localhost> (raw)
In-Reply-To: <CAK5ve-+96fNSF0cV1gefzgJNFX-nefZ08HWupPirQYauecEQYw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Thu, 20 Jun 2013 16:49:54 -0700, Bryan Wu <cooloney-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Hi Rob,
>
> Is this patch good for merging?
>
> In Alex's one patch to add device tree supporting for a leds driver,
> we got building errors due to miss definitions of some of_xxx api
> functions.
>
> It looks obviously to me that we need to fix this in device tree core
> instead put #ifdef CONFIG_OF everywhere.
Actually, the reason those things aren't universally defined is to catch
exactly what it caught. The "leds-mc13783: Add devicetree support" patch
interleaves DT and non-DT parsing which isn't generally a good idea. The
DT parsing code should be shuffled off into a separate function and/or
contained with "if (IS_ENABLED(CONFIG_OF)) {}".
So, no, I don't want this patch merged.
g.
>
> Thanks,
> -Bryan
>
> On Tue, Jun 18, 2013 at 9:35 AM, Alexander Shiyan <shc_work-JGs/UdohzUI@public.gmane.org> wrote:
> >> Perhaps a more specific subject.
> >
> > I can just specify stub function names in the subject.
> > Is this enough?
> >
> >> On 06/17/2013 12:24 PM, Alexander Shiyan wrote:
> >> > Patch adds of_get_next_child and of_get_next_available_child
> >> > stubs for non-OF builds.
> >> >
> >> > Signed-off-by: Alexander Shiyan <shc_work-JGs/UdohzUI@public.gmane.org>
> >> > ---
> >>
> >> What changed for v2?
> >
> > v1 not contain "inline" for prototypes.
> >
> >> > include/linux/of.h | 16 ++++++++++++++--
> >> > 1 file changed, 14 insertions(+), 2 deletions(-)
> >> >
> >> > diff --git a/include/linux/of.h b/include/linux/of.h
> >> > index 1fd08ca..df0e644 100644
> >> > --- a/include/linux/of.h
> >> > +++ b/include/linux/of.h
> >> > @@ -366,8 +366,17 @@ static inline bool of_have_populated_dt(void)
> >> > return false;
> >> > }
> >> >
> >> > -#define for_each_child_of_node(parent, child) \
> >> > - while (0)
> >> > +static struct device_node *of_get_next_child(const struct device_node *node,
> >> > + struct device_node *prev)
> >> > +{
> >> > + return NULL;
> >> > +}
> >> > +
> >> > +static struct device_node *of_get_next_available_child(
> >> > + const struct device_node *node, struct device_node *prev)
> >> > +{
> >> > + return NULL;
> >> > +}
> >> >
> >> > static inline struct device_node *of_get_child_by_name(
> >> > const struct device_node *node,
> >> > @@ -376,6 +385,9 @@ static inline struct device_node *of_get_child_by_name(
> >> > return NULL;
> >> > }
> >> >
> >> > +#define for_each_child_of_node(parent, child) \
> >>
> >> parent and child need unused annotations to avoid unused variable warnings.
> >
> > This define has been moved just for keep same order as for OF-version.
> >
> > ---
--
email sent from notmuch.vim plugin
next prev parent reply other threads:[~2013-06-21 0:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 17:24 [PATCH] of: Add more stubs for non-OF builds Alexander Shiyan
[not found] ` <1371489882-11143-1-git-send-email-shc_work-JGs/UdohzUI@public.gmane.org>
2013-06-18 16:25 ` Rob Herring
[not found] ` <51C089F6.2060902-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-06-18 16:35 ` Alexander Shiyan
[not found] ` <1371573337.452797583-x9YND1UlJWJsdVUOrk1QfQ@public.gmane.org>
2013-06-20 23:49 ` Bryan Wu
[not found] ` <CAK5ve-+96fNSF0cV1gefzgJNFX-nefZ08HWupPirQYauecEQYw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-21 0:26 ` Grant Likely [this message]
2013-06-21 0:36 ` Bryan Wu
[not found] ` <CAK5ve-JX1BC-jdpSzBx_en_o4FYjie-1GRL39B18NywUvXAHrg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-21 10:21 ` Grant Likely
2013-06-21 14:17 ` Re[2]: " Alexander Shiyan
[not found] ` <1371824246.856851759-pyBXd9eNxi0edp2WBT/QOw@public.gmane.org>
2013-06-21 17:13 ` Bryan Wu
2013-06-21 17:21 ` Re[4]: " Alexander Shiyan
[not found] ` <1371835275.689989846-g6/BKhZsNKQedp2WBT/QOw@public.gmane.org>
2013-06-21 18:22 ` Grant Likely
2013-06-21 18:35 ` Re[6]: " Alexander Shiyan
[not found] ` <1371839716.602513920-Sq8Ym99z60Iedp2WBT/QOw@public.gmane.org>
2013-06-21 18:56 ` Grant Likely
[not found] ` <CACxGe6uqng-s4KtSwQ-MEUQ3Ed9_moNw_KvZeaPoN2OaGZnNWA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-27 9:50 ` Grant Likely
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=20130621002607.F24A63E093E@localhost \
--to=grant.likely-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=cooloney-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=linux-leds-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org \
--cc=shc_work-JGs/UdohzUI@public.gmane.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;
as well as URLs for NNTP newsgroup(s).