public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Balaji Rao <balajirrao@openmoko.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, sameo@openedhand.com
Subject: Re: [PATCH V3 0/7] PCF50633 support
Date: Tue, 13 Jan 2009 12:17:45 +0530	[thread overview]
Message-ID: <20090113064743.GA3218@fedora.yogi> (raw)
In-Reply-To: <20090112144434.eeb1640d.akpm@linux-foundation.org>

On Mon, Jan 12, 2009 at 02:44:34PM -0800, Andrew Morton wrote:
> On Mon, 05 Jan 2009 23:42:42 +0530
> Balaji Rao <balajirrao@openmoko.org> wrote:
> 
> > The following series implements support for NXP PCF50633. It's basically
> > an I2C device with 9 regulators, an ADC, a PMIC, a Battery Charger
> > and a RTC.
> > 
> > This chip is used in Openmoko Neo Freerunner mobile phone.
> > 
> > The specs are open and are available at 
> > http://people.openmoko.org/tony_tu/GTA02/datasheet/PMU/PCF50633DS_02.pdf
> > 
> > ---
> > Balaji Rao (7):
> >       mfd: PCF50633 core driver
> >       mfd: PCF50633 adc driver
> >       mfd: PCF50633 gpio support
> >       rtc: PCF50633 rtc driver
> >       power_supply: PCF50633 battery charger driver
> >       input: PCF50633 input driver
> >       regulator: PCF50633 pmic driver
> 
> You have patches here which should strictly be merged by various
> different subsystem trees.  That gets tricky because presumably there
> are dependencies.
> 
> What _are_ the dependencies here?  Do patches 2-7 depend upon #1, perhaps?
> 

yes, patches 2-7 depend on the first one.

> If so, then one approach would be to merge the first patch into
> mainline now then trickle the rest out into subsystem trees.
> 
> Or, with suitable acks, I can merge the lot.  Perhaps into 2.6.29..
> 

Andrew,

Samuel had sent a git-pull for the linux-mfd tree containing this series a couple
of days ago and now I see that it's merged. So, I think you can remove
these from -mm.

Thanks,
Balaji

      reply	other threads:[~2009-01-13  6:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-05 18:12 [PATCH V3 0/7] PCF50633 support Balaji Rao
2009-01-05 18:13 ` [PATCH V3 1/7] mfd: PCF50633 core driver Balaji Rao
2009-01-05 18:13 ` [PATCH V3 2/7] mfd: PCF50633 adc driver Balaji Rao
2009-01-05 18:14 ` [PATCH V3 3/7] mfd: PCF50633 gpio support Balaji Rao
2009-01-05 18:14 ` [PATCH V3 4/7] rtc: PCF50633 rtc driver Balaji Rao
2009-01-06 21:52   ` Alessandro Zummo
2009-01-05 18:14 ` [PATCH V3 5/7] power_supply: PCF50633 battery charger driver Balaji Rao
2009-01-05 18:15 ` [PATCH V3 6/7] input: PCF50633 input driver Balaji Rao
2009-01-05 18:15 ` [PATCH V3 7/7] regulator: PCF50633 pmic driver Balaji Rao
2009-01-12 22:44 ` [PATCH V3 0/7] PCF50633 support Andrew Morton
2009-01-13  6:47   ` Balaji Rao [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=20090113064743.GA3218@fedora.yogi \
    --to=balajirrao@openmoko.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sameo@openedhand.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