From: Kevin Hilman <khilman@ti.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: "Cousson, Benoit" <b-cousson@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 2/2] OMAP: omap_device: Add a method to build an omap_device from a DT node
Date: Thu, 29 Sep 2011 13:46:39 -0700 [thread overview]
Message-ID: <87vcsboz4g.fsf@ti.com> (raw)
In-Reply-To: <20110929173006.GG6800@ponder.secretlab.ca> (Grant Likely's message of "Thu, 29 Sep 2011 12:30:06 -0500")
Grant Likely <grant.likely@secretlab.ca> writes:
> On Wed, Sep 28, 2011 at 10:47:32AM -0700, Kevin Hilman wrote:
>> "Cousson, Benoit" <b-cousson@ti.com> writes:
>>
>> > Hi Grant, Kevin,
>> >
>> > Should I go ahead with this version and repost the series with that
>> > third patch?
>>
>> Fine with me.
>>
>> Grant let me know if you prefer if I merge it (with your ack) with the
>> rest of the series or if you want to take it to avoid conflicts.
>
> I'm happy with the way things have gone. Go ahead and add my Ack and
> merge it through your tree. I'd like to avoid the conflicts.
Thanks, I think keeping this series together will be smoothest.
Adding your ack, and queuing for v3.2 (branch: for_3.2/omap_device-2)
Kevin
next prev parent reply other threads:[~2011-09-29 20:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 20:52 [PATCH v3 0/2] OMAP: omap_device: Add a method to build an omap_device from a DT node Benoit Cousson
2011-09-22 20:52 ` [PATCH v3 1/2] OMAP: omap_device: Add omap_device_[alloc|delete] for DT integration Benoit Cousson
2011-09-22 20:52 ` [PATCH v3 2/2] OMAP: omap_device: Add a method to build an omap_device from a DT node Benoit Cousson
2011-09-27 1:46 ` Grant Likely
2011-09-27 16:04 ` Cousson, Benoit
2011-09-28 16:11 ` Cousson, Benoit
2011-09-28 17:47 ` Kevin Hilman
2011-09-29 17:30 ` Grant Likely
2011-09-29 20:46 ` Kevin Hilman [this message]
2011-09-26 22:38 ` [PATCH v3 0/2] " Kevin Hilman
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=87vcsboz4g.fsf@ti.com \
--to=khilman@ti.com \
--cc=b-cousson@ti.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.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