mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Miao <eric.y.miao@gmail.com>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: eric.miao@marvell.com, broonie@opensource.wolfsonmicro.com,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.arm.linux.org.uk,
	Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: Patch to add mioa701 glue for voltage regulation
Date: Tue, 28 Apr 2009 09:13:41 +0800	[thread overview]
Message-ID: <f17812d70904271813t2c67d929n67c84bb86f450e35@mail.gmail.com> (raw)
In-Reply-To: <87d4ax7qf3.fsf@free.fr>

On Tue, Apr 28, 2009 at 5:11 AM, Robert Jarzmik <robert.jarzmik@free.fr> wrote:
> Liam Girdwood <lrg@slimlogic.co.uk> writes:
>
>> On Thu, 2009-04-23 at 20:30 +0200, Robert Jarzmik wrote:
>>> Hi Mark and Eric,
>>>
>>> I have that patch which adds voltage regulation definitions to mioa701
>>> board. The trick is, this patch depends on two others :
>>>
>>>  - one which will be merged through Mark's regulator tree.
>>>    This one is mandatory as a compiling dependency exists through include files.
>>>
>>>  - one which will be merge through Eric pxa tree.
>>>    This is the cpufreq one, and has a "very weak" dependency, as only the
>>>    "vcc_core" name _is_ the dependency.
>>>
>>> I think the easiest way to solve the compiling dependency
>>> (include/linux/regulator.max1586.h) is to make that patch go through regulator
>>> tree as well for linux-next, even if it's arm machine specific, don't you ?
>>>
>>
>> If fine with this going through regulator providing I get an ACK from
>> Eric.
>
> Eric,
>
> Since Liam took the max1586 regulator through his tree, would you state if you
> ack that please ?
>

I'd really be happy to. However, my concern is that this patch modifies
arch/arm/mach-pxa/mioa701.c _only_, so it would be better to go through
my tree so that I can manage all the potential merge conflicts. There are
several other changes to mioa701.c and I expect the content in
arch/arm/mach-pxa/* to be heavily changed due to recent addition
of pxa168/pxa910 support.

The issue of dependency, as was always before, can be resolved by
putting this into 'pending' and monitoring the status of merge window
before sending the PULL request.

Liam,

Sounds OK to you?

  reply	other threads:[~2009-04-28  1:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23 18:30 Robert Jarzmik
2009-04-23 19:13 ` Mark Brown
2009-04-24  9:42 ` Liam Girdwood
2009-04-27 21:11   ` Robert Jarzmik
2009-04-28  1:13     ` Eric Miao [this message]
2009-04-28 10:38       ` Liam Girdwood
2009-04-28  8:23     ` Mark Brown

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=f17812d70904271813t2c67d929n67c84bb86f450e35@mail.gmail.com \
    --to=eric.y.miao@gmail.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=eric.miao@marvell.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=robert.jarzmik@free.fr \
    /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

all inboxes | Powered by JetHome®