Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753505AbZKTMgk (ORCPT ); Fri, 20 Nov 2009 07:36:40 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753386AbZKTMgj (ORCPT ); Fri, 20 Nov 2009 07:36:39 -0500 Received: from opensource.wolfsonmicro.com ([80.75.67.52]:51356 "EHLO opensource2.wolfsonmicro.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753123AbZKTMgh (ORCPT ); Fri, 20 Nov 2009 07:36:37 -0500 Date: Fri, 20 Nov 2009 12:36:42 +0000 From: Mark Brown To: Liam Girdwood Cc: Samuel Ortiz , "Keski-Saari Juha.1 (EXT-Teleca/Helsinki)" , "Peter 'p2' De Schrijver" , "Valentin Eduardo (Nokia-D/Helsinki)" , "dbrownell@users.sourceforge.net" , "tony@atomide.com" , "linux-kernel@vger.kernel.org" , "Hunter Adrian (Nokia-D/Helsinki)" , "amit.kucheria@verdurent.com" , "dtor@mail.ru" , "Kristo Tero (Nokia-D/Tampere)" Subject: Re: [PATCH 1/1] Add all TWL4030 regulators to Regulator framework Message-ID: <20091120123642.GA23283@rakim.wolfsonmicro.main> References: <20091118133938.GE6592@rakim.wolfsonmicro.main> <20091118143609.GD2832@esdhcp037198.research.nokia.com> <20091118144145.GA16852@rakim.wolfsonmicro.main> <4B04EDE8.1010906@nokia.com> <20091119092412.GA4696@codecarver.research.nokia.com> <20091119103054.GC9763@rakim.wolfsonmicro.main> <20091120100633.GE3733@sortiz.org> <1258713145.3640.11.camel@odin> <20091120112812.GC20236@rakim.wolfsonmicro.main> <1258719703.3640.41.camel@odin> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1258719703.3640.41.camel@odin> X-Cookie: Used staples are good with SOY SAUCE! User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 976 Lines: 23 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/