All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Ribeiro <drwyrm@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Samuel Ortiz <sameo@linux.intel.com>
Cc: Liam Girdwood <lrg@slimlogic.co.uk>,
	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: Sat, 27 Jun 2009 14:26:58 -0300	[thread overview]
Message-ID: <1246123618.3727.29.camel@brutus> (raw)
In-Reply-To: <20090627105150.GA4780@sirena.org.uk>

[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]

Em Sáb, 2009-06-27 às 11:51 +0100, Mark Brown escreveu:
> On Sat, Jun 27, 2009 at 12:18:02AM -0300, Daniel Ribeiro wrote:
> > Add (partial) support for the voltage regulators on the PCAP2 PMIC.
> > 
> > Signed-off-by: Daniel Ribeiro <drwyrm@gmail.com>
> 
> Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> 
> Looks good.

Thanks.

> > Mark, can you please assert that this only gets merged after Samuel has
> > a chance to merge the set_bits patch? Thanks!
> 
> It's Liam who manages the regulator tree, though given the set_bits()
> patch perhaps this one might end up getting merged via the MFD tree (or
> both via the regulator tree).

I prefer the set_bits() patch going through the MFD tree. I sent some
other fixes, and a patch to solve a similar race issue for the ADC/TS
driver.

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.

-- 
Daniel Ribeiro

[-- Attachment #2: Esta é uma parte de mensagem assinada digitalmente --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-06-27 17:27 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 [this message]
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

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=1246123618.3727.29.camel@brutus \
    --to=drwyrm@gmail.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=openezx-devel@lists.openezx.org \
    --cc=sameo@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.