From: Samuel Ortiz <sameo@linux.intel.com>
To: Liam Girdwood <lrg@slimlogic.co.uk>
Cc: Daniel Ribeiro <drwyrm@gmail.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
openezx-devel <openezx-devel@lists.openezx.org>
Subject: Re: [PATCHv3] PCAP regulator driver (for 2.6.32)
Date: Fri, 3 Jul 2009 12:43:23 +0200 [thread overview]
Message-ID: <20090703104321.GB4176@sortiz.org> (raw)
In-Reply-To: <1246615901.4438.1107.camel@vega.slimlogic.co.uk>
On Fri, Jul 03, 2009 at 11:11:41AM +0100, Liam Girdwood wrote:
> On Fri, 2009-07-03 at 11:35 +0200, Samuel Ortiz wrote:
> > Hi Daniel,
> >
> > On Sat, Jun 27, 2009 at 02:26:58PM -0300, Daniel Ribeiro wrote:
>
> > >
> > > Ideally, Samuel would push the PCAP patches on -rc phase, so the
> > > sub-drivers can all be merged through the respective subsystem trees on
> > > the .32 merge window.
> > If that's ok with Liam, I'll take the regulator patch. Most of the pcap
> > patches are not rc material, so they will be merged along with the regulator
> > driver with the next merge window.
> >
> > Liam, if you're fine with this patch, could you please SOB it ? Thanks.
>
> Signed-off-by: Liam Girdwood <lrg@slimlogic.co.uk>
Thanks, patch applied to my for-next branch.
Cheers,
Samuel.
> Thanks!
>
> Liam
>
>
--
Intel Open Source Technology Centre
http://oss.intel.com/
prev parent reply other threads:[~2009-07-03 10:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-27 3:18 [PATCHv3] PCAP regulator driver (for 2.6.32) Daniel Ribeiro
2009-06-27 10:51 ` Mark Brown
2009-06-27 17:26 ` Daniel Ribeiro
2009-06-29 10:23 ` Liam Girdwood
2009-06-29 10:28 ` Liam Girdwood
2009-07-03 9:35 ` Samuel Ortiz
2009-07-03 10:11 ` Liam Girdwood
2009-07-03 10:43 ` Samuel Ortiz [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=20090703104321.GB4176@sortiz.org \
--to=sameo@linux.intel.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=drwyrm@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=openezx-devel@lists.openezx.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