From: Linus Walleij <linus.walleij@linaro.org>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/10] Ux500 PRCMU into MFD and update deps
Date: Mon, 16 May 2011 01:20:24 +0200 [thread overview]
Message-ID: <BANLkTimSpzavQruy1AT2JEh4g1ULdwZPOA@mail.gmail.com> (raw)
In-Reply-To: <20110511144119.GC23897@sortiz-mobl>
2011/5/11 Samuel Ortiz <sameo@linux.intel.com>:
> On Wed, May 11, 2011 at 02:39:03PM +0200, Linus Walleij wrote:
>> 2011/5/6 Linus Walleij <linus.walleij@stericsson.com>:
>>
>> > I will attempt to slim this down a bit, mainly the set is a
>> > review point for the MFD maintainer to check out if the PRCMU
>> > driver fits within MFD.
>>
>> Sam will you be able to provide some feedback on this so I know
>> whether I shall plan to polish it up for the 2.6.40 merge window or
>> not?
>
> I quickly looked at this patchset, and I hope to be able to review it better
> next week. But overall I think this fits into the MFD mapped registers model.
> So please go ahead and prepare this stuff for the .40 merge window (I'd
> appreciate to see the "slimming this down a bit" part, while I expect to come
> back to you with some more comments by next week.
OK I have broken it into a *bit* smaller chunks by making a
(yet complex) movement patch to get the stuff out of the mach-ux500
which I then patch to an acceptable level.
I also pushed non-conflicting parts (all but 2 patches) to next
for testing, applying them in parallell in MFD should work just
fine, then I can take them off my branch.
Thanks,
Linus Walleij
prev parent reply other threads:[~2011-05-15 23:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 13:04 Linus Walleij
2011-05-11 12:39 ` Linus Walleij
2011-05-11 14:41 ` Samuel Ortiz
2011-05-15 23:20 ` Linus Walleij [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=BANLkTimSpzavQruy1AT2JEh4g1ULdwZPOA@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.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 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®