From: Grant Likely <grant.likely@secretlab.ca>
To: Stephen Warren <swarren@nvidia.com>
Cc: devicetree-discuss@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt: add empty for_each_child_of_node, of_find_property
Date: Thu, 22 Sep 2011 11:29:44 -0600 [thread overview]
Message-ID: <20110922172944.GM17168@ponder.secretlab.ca> (raw)
In-Reply-To: <1316632990-12876-1-git-send-email-swarren@nvidia.com>
On Wed, Sep 21, 2011 at 01:23:10PM -0600, Stephen Warren wrote:
> The patch adds a couple empty functions for non-dt build, so that
> drivers migrating to dt can save some '#ifdef CONFIG_OF'.
>
> Signed-off-by: Stephen Warren <swarren@nvidia.com>
> ---
Applied, thanks.
g.
> Unfortunately, I screwed up and my recent sdhci-tegra.c changes rely on this
> change to compile without CONFIG_OF; I really need to stop doing my test-
> builds in a single branch will all my outstanding changes present:-(
>
> include/linux/of.h | 10 ++++++++++
> 1 files changed, 10 insertions(+), 0 deletions(-)
>
> diff --git a/include/linux/of.h b/include/linux/of.h
> index 9180dc5..1fc5875 100644
> --- a/include/linux/of.h
> +++ b/include/linux/of.h
> @@ -242,6 +242,16 @@ static inline bool of_have_populated_dt(void)
> return false;
> }
>
> +#define for_each_child_of_node(parent, child) \
> + while (0)
> +
> +static inline struct property *of_find_property(const struct device_node *np,
> + const char *name,
> + int *lenp)
> +{
> + return NULL;
> +}
> +
> static inline int of_property_read_u32_array(const struct device_node *np,
> const char *propname,
> u32 *out_values, size_t sz)
> --
> 1.7.0.4
>
prev parent reply other threads:[~2011-09-22 17:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 19:23 [PATCH] dt: add empty for_each_child_of_node, of_find_property Stephen Warren
2011-09-22 17:29 ` Grant Likely [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=20110922172944.GM17168@ponder.secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swarren@nvidia.com \
/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).