[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091120123642.GA23283@rakim.wolfsonmicro.main>
Date: Fri, 20 Nov 2009 12:36:42 +0000
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Liam Girdwood <lrg@...mlogic.co.uk>
Cc: Samuel Ortiz <sameo@...ux.intel.com>,
"Keski-Saari Juha.1 (EXT-Teleca/Helsinki)"
<ext-juha.1.keski-saari@...ia.com>,
Peter 'p2' De Schrijver <peter.de-schrijver@...ia.com>,
"Valentin Eduardo (Nokia-D/Helsinki)" <eduardo.valentin@...ia.com>,
"dbrownell@...rs.sourceforge.net" <dbrownell@...rs.sourceforge.net>,
"tony@...mide.com" <tony@...mide.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Hunter Adrian (Nokia-D/Helsinki)" <adrian.hunter@...ia.com>,
"amit.kucheria@...durent.com" <amit.kucheria@...durent.com>,
"dtor@...l.ru" <dtor@...l.ru>,
"Kristo Tero (Nokia-D/Tampere)" <Tero.Kristo@...ia.com>
Subject: Re: [PATCH 1/1] Add all TWL4030 regulators to Regulator framework
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists