From: Wolfram Sang <wsa@the-dreams.de>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Rob Herring <robherring2@gmail.com>,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Pantelis Antoniou <panto@antoniou-consulting.com>
Subject: Re: [PATCH] of: Empty node & property flag accessors when !OF
Date: Sun, 22 Mar 2015 22:03:15 +0100 [thread overview]
Message-ID: <20150322210315.GA974@katana> (raw)
In-Reply-To: <20150320121223.16D69C4076B@trevor.secretlab.ca>
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
On Fri, Mar 20, 2015 at 12:12:23PM +0000, Grant Likely wrote:
> On Thu, 22 Jan 2015 17:13:51 -0600
> , Rob Herring <robherring2@gmail.com>
> wrote:
> > +Wolfram
> >
> > On Wed, Jan 21, 2015 at 11:05 AM, Pantelis Antoniou
> > <pantelis.antoniou@konsulko.com> wrote:
> > > Introduce empty node and property flag accessors when CONFIG_OF is not
> > > defined.
> > > This allows us to use them without ifdef'ing them in places where it
> > > makes sense to do so.
> > >
> > > Signed-off-by: Pantelis Antoniou <pantelis.antoniou@konsulko.com>
> >
> > Acked-by: Rob Herring <robh@kernel.org>
> >
> > I've asked Wolfram to apply. While not a fix itself, this is needed
> > for an I2C related fix for 3.19.
>
> I don't see this in mainline or linux-next, so I've applied to my tree.
> Thanks.
Thanks! I didn't have the original patch and asked for a resend. That
never happened, so it slipped through.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-03-22 21:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 17:05 [PATCH] of: Empty node & property flag accessors when !OF Pantelis Antoniou
2015-01-22 23:13 ` Rob Herring
2015-03-20 12:12 ` Grant Likely
2015-03-22 21:03 ` Wolfram Sang [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=20150322210315.GA974@katana \
--to=wsa@the-dreams.de \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=panto@antoniou-consulting.com \
--cc=robherring2@gmail.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