From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Liam Girdwood <lrg@slimlogic.co.uk>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
"Keski-Saari Juha.1 (EXT-Teleca/Helsinki)"
<ext-juha.1.keski-saari@nokia.com>,
"Peter 'p2' De Schrijver" <peter.de-schrijver@nokia.com>,
"Valentin Eduardo (Nokia-D/Helsinki)"
<eduardo.valentin@nokia.com>,
"dbrownell@users.sourceforge.net"
<dbrownell@users.sourceforge.net>,
"tony@atomide.com" <tony@atomide.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Hunter Adrian (Nokia-D/Helsinki)" <adrian.hunter@nokia.com>,
"amit.kucheria@verdurent.com" <amit.kucheria@verdurent.com>,
"dtor@mail.ru" <dtor@mail.ru>,
"Kristo Tero (Nokia-D/Tampere)" <Tero.Kristo@nokia.com>
Subject: Re: [PATCH 1/1] Add all TWL4030 regulators to Regulator framework
Date: Fri, 20 Nov 2009 12:36:42 +0000 [thread overview]
Message-ID: <20091120123642.GA23283@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1258719703.3640.41.camel@odin>
On Fri, Nov 20, 2009 at 12:21:43PM +0000, Liam Girdwood wrote:
> On Fri, 2009-11-20 at 11:28 +0000, Mark Brown wrote:
> > Either the existing twl4030-mfd branch or split patches work for me.
> What's the upstream path for your twl4030-mfd ASoC branch ?
ALSA with bits also pulled into the OMAP tree.
> Regulator + mfd patches either go upstream via the regulator or mfd
> repositories.
Yes, ideally - the existing stuff is going via ALSA since the MFD and
ASoC sides can't be split up sensibly without breaking bisection.
Another option would be to hold off on applying the patch until things
have settled down in the merge window and then push it via regulator -
the ALSA tree normally goes in early in the merge window.
next prev parent reply other threads:[~2009-11-20 12:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 11:45 [PATCH 0/1] Add all TWL4030 regulators to Regulator framework Juha Keski-Saari
2009-11-18 11:46 ` [PATCH 1/1] " Juha Keski-Saari
2009-11-18 13:39 ` Mark Brown
2009-11-18 14:36 ` Eduardo Valentin
2009-11-18 14:41 ` Mark Brown
2009-11-19 7:04 ` Juha Keski-Saari
2009-11-19 9:24 ` Peter 'p2' De Schrijver
2009-11-19 10:30 ` Mark Brown
2009-11-20 10:06 ` Samuel Ortiz
2009-11-20 10:32 ` Liam Girdwood
2009-11-20 11:28 ` Mark Brown
2009-11-20 12:21 ` Liam Girdwood
2009-11-20 12:36 ` Mark Brown [this message]
2009-11-23 13:26 ` Juha Keski-Saari
2009-11-18 17:51 ` Dmitry Torokhov
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=20091120123642.GA23283@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Tero.Kristo@nokia.com \
--cc=adrian.hunter@nokia.com \
--cc=amit.kucheria@verdurent.com \
--cc=dbrownell@users.sourceforge.net \
--cc=dtor@mail.ru \
--cc=eduardo.valentin@nokia.com \
--cc=ext-juha.1.keski-saari@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=peter.de-schrijver@nokia.com \
--cc=sameo@linux.intel.com \
--cc=tony@atomide.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