From: lrg@slimlogic.co.uk (Liam Girdwood)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 4/5] mfd: regulator: max8998: voltages and GPIOs defined at platform data structure
Date: Mon, 04 Oct 2010 11:09:49 +0100 [thread overview]
Message-ID: <1286186989.3148.19.camel@odin> (raw)
In-Reply-To: <20101004084646.4de3714d@lmajewski.digital.local>
On Mon, 2010-10-04 at 08:46 +0200, Lukasz Majewski wrote:
> On Sat, 02 Oct 2010 14:33:33 +0100
> Liam Girdwood <lrg@slimlogic.co.uk> wrote:
>
> > On Mon, 2010-09-27 at 20:43 +0200, Samuel Ortiz wrote:
> > > Hi Lukasz,
> > >
> > > On Mon, Sep 27, 2010 at 02:32:26PM +0200, Lukasz Majewski wrote:
> > > > Signed-off-by: Lukasz Majewski <l.majewski@samsung.com>
> > > > Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
> > > Fine with me:
> > > Acked-by: Samuel Ortiz <sameo@linux.intel.com>
> > >
> >
> > Lukasz, this is not applying against the regulator next tree.
> > Can you redo and add Mark and Samuels Acks.
> >
> > Thanks
> >
> > Liam
>
> Hi Liam,
>
> I've fetched the newest voltage-2.6/for-next and merge it with newest
> mfd-2.6/for next. After that all patches are applying and kernel is
> building without errors.
>
> The problem with this patch series is that it "touches" two
> repositories: voltage-2.6 and mfd-2.6.
>
> I'm a bit confused how such situation should be resolved, since it
> involves two separate repositories (and two maintainers to cooperate).
>
You should only base your patches on one tree for upstreaming and since
this series mostly touches regulator it's best base against the
regulator tree.
Liam
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2010-10-04 10:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 12:32 [PATCH v3 0/5] mfd: regulator: max8998: BUCK1/2 control augmented by GPIO pins Lukasz Majewski
2010-09-27 12:32 ` [PATCH v3 1/5] mfd: regulator: max8998: separate set_voltage for ldo and buck Lukasz Majewski
2010-09-27 16:01 ` Mark Brown
2010-09-27 12:32 ` [PATCH v3 2/5] mfd: regulator: max8998: Support for ICs compliant with max8998 Lukasz Majewski
2010-09-27 16:03 ` Mark Brown
2010-09-27 12:32 ` [PATCH v3 3/5] mfd: regulator: max8998: BUCK1/2 internal voltages and indexes defined Lukasz Majewski
2010-09-27 16:04 ` Mark Brown
2010-09-27 12:32 ` [PATCH v3 4/5] mfd: regulator: max8998: voltages and GPIOs defined at platform data structure Lukasz Majewski
2010-09-27 18:43 ` Samuel Ortiz
2010-10-02 13:33 ` Liam Girdwood
2010-10-04 6:46 ` Lukasz Majewski
2010-10-04 10:09 ` Liam Girdwood [this message]
2010-10-04 11:36 ` Lukasz Majewski
2010-10-06 7:05 ` Marek Szyprowski
2010-10-06 10:46 ` Liam Girdwood
2010-10-18 23:47 ` Samuel Ortiz
2010-10-19 9:22 ` Liam Girdwood
2010-09-27 12:32 ` [PATCH v3 5/5] mfd: regulator: max8998: BUCK1/2 voltage change with use of GPIOs Lukasz Majewski
2010-09-27 16:13 ` Mark Brown
2010-09-27 18:38 ` [PATCH v3 0/5] mfd: regulator: max8998: BUCK1/2 control augmented by GPIO pins Liam Girdwood
2010-09-27 18:40 ` Liam Girdwood
2010-09-27 18:45 ` 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=1286186989.3148.19.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=linux-arm-kernel@lists.infradead.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 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.