From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Ashish Jangam <Ashish.Jangam@kpitcummins.com>,
Lars-Peter Clausen <lars@metafoo.de>,
"rpurdie@rpsys.net" <rpurdie@rpsys.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
David Dajun Chen <Dajun.Chen@diasemi.com>
Subject: Re: [PATCHv2 -next] LEDS: LED module of DA9052 PMIC driver
Date: Wed, 18 May 2011 23:15:42 +0100 [thread overview]
Message-ID: <20110518221542.GB20909@sirena.org.uk> (raw)
In-Reply-To: <20110518122332.94d4fdb9.akpm@linux-foundation.org>
On Wed, May 18, 2011 at 12:23:32PM -0700, Andrew Morton wrote:
> A way to proceed with this patchset is to get the core PMIC_DA9052
> support patch merged and to then send the various dependent patches to
> the relevant maintainers.
...
> An alternative way of getting it all merged up is for us to ask Samuel
> to merge _all_ the patches, after receiving suitable acks and reviews
> from suitable people. Or I can do that.
> I think the second way is better. Sam?
The way these things have often been dealt with is to just merge the
code via the various trees and rely on -next for build testing - they
won't cause bisection issues as the lack of the MFD will prevent the
config being enabled, everything goes in in a single release and we
still get to keep all the code for each subsystem together.
Of course, since the code isn't even signed off we've got a way to go
yet...
prev parent reply other threads:[~2011-05-18 22:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 11:52 Ashish Jangam
2011-05-18 19:23 ` Andrew Morton
2011-05-18 22:15 ` Mark Brown [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=20110518221542.GB20909@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Ashish.Jangam@kpitcummins.com \
--cc=Dajun.Chen@diasemi.com \
--cc=akpm@linux-foundation.org \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@rpsys.net \
/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®