From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Thierry Reding
<thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Cc: Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>
Subject: Re: [PATCH 1/2] dt: Add empty of_property_match_string() function
Date: Fri, 27 Apr 2012 10:45:54 -0600 [thread overview]
Message-ID: <20120427164554.2F7E33E0B4D@localhost> (raw)
In-Reply-To: <20120426190112.GA28018-RM9K5IK7kjIQXX3q8xo1gnVAuStQJXxyR5q1nwbD4aMs9pC9oP6+/A@public.gmane.org>
On Thu, 26 Apr 2012 21:01:12 +0200, Thierry Reding <thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org> wrote:
> * Thierry Reding wrote:
> > This commit adds an empty of_property_match_string() function for
> > !CONFIG_OF builds.
>
> Grant, Rob,
>
> can these two patches be queued for 3.5? I need them to build the PWM
> subsystem for !OF builds.
I could merge them, but can you point me at the code that needs them?
I get a little nervous when OF-specific stretches of code get compiled
when !CONFIG_OF. In a lot of cases the OF data decoding should be in
a separate function that gets completely selected out. That isn't
always the case of course, but I do like to put a bit of back-pressure
on this issue.
g.
next prev parent reply other threads:[~2012-04-27 16:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 14:23 [PATCH 1/2] dt: Add empty of_property_match_string() function Thierry Reding
[not found] ` <1334327016-8949-1-git-send-email-thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>
2012-04-13 14:23 ` [PATCH 2/2] dt: Add empty of_parse_phandle_with_args() function Thierry Reding
2012-04-26 19:01 ` [PATCH 1/2] dt: Add empty of_property_match_string() function Thierry Reding
[not found] ` <20120426190112.GA28018-RM9K5IK7kjIQXX3q8xo1gnVAuStQJXxyR5q1nwbD4aMs9pC9oP6+/A@public.gmane.org>
2012-04-27 16:45 ` Grant Likely [this message]
2012-04-27 20:41 ` Thierry Reding
[not found] ` <20120427204154.GA12617-RM9K5IK7kjIQXX3q8xo1gnVAuStQJXxyR5q1nwbD4aMs9pC9oP6+/A@public.gmane.org>
2012-04-27 20:53 ` Thierry Reding
[not found] ` <20120427205307.GA16099-RM9K5IK7kjIQXX3q8xo1gnVAuStQJXxyR5q1nwbD4aMs9pC9oP6+/A@public.gmane.org>
2012-06-01 5:59 ` Thierry Reding
[not found] ` <20120601055920.GA15874-RM9K5IK7kjIyiCvfTdI0JKcOhU4Rzj621B7CTYaBSLdn68oJJulU0Q@public.gmane.org>
2012-06-13 7:02 ` Thierry Reding
[not found] ` <20120613070256.GB5670-RM9K5IK7kjIQXX3q8xo1gnVAuStQJXxyR5q1nwbD4aMs9pC9oP6+/A@public.gmane.org>
2012-06-13 15:20 ` 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=20120427164554.2F7E33E0B4D@localhost \
--to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org \
--cc=thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@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).