Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755708Ab0BBH1Y (ORCPT ); Tue, 2 Feb 2010 02:27:24 -0500 Received: from cantor2.suse.de ([195.135.220.15]:39271 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755338Ab0BBH1V (ORCPT ); Tue, 2 Feb 2010 02:27:21 -0500 Date: Tue, 02 Feb 2010 08:27:19 +0100 Message-ID: From: Takashi Iwai To: Stephen Rothwell Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Mark Brown , Samuel Ortiz Subject: Re: linux-next: sound tree build failure In-Reply-To: <20100202124711.d8cdc220.sfr@canb.auug.org.au> References: <20100202124711.d8cdc220.sfr@canb.auug.org.au> User-Agent: Wanderlust/2.15.6 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.7 Emacs/23.1 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1552 Lines: 44 At Tue, 2 Feb 2010 12:47:11 +1100, Stephen Rothwell wrote: > > Hi Takashi, > > Today's linux-next build (x86_64 allmodconfig) failed like this: > > sound/soc/codecs/wm8994.c:30:35: error: linux/mfd/wm8994/core.h: No such file or directory > sound/soc/codecs/wm8994.c:31:40: error: linux/mfd/wm8994/registers.h: No such file or directory > sound/soc/codecs/wm8994.c:32:36: error: linux/mfd/wm8994/pdata.h: No such file or directory > sound/soc/codecs/wm8994.c:33:35: error: linux/mfd/wm8994/gpio.h: No such file or directory > > And went down hill form there :-( Ah, sorry, this driver didn't hit in my quick test in the last evening before pushing. > Caused by commit 9e6e96a197a03752d39a63e4f83e0b707ccedad7 ("ASoC: Add > WM8994 CODEC driver"). I presume that this commit depends on commits > currently only in the mfd tree ... Yep, looks so. > I have used the sound tree from next-20100201 for today. > > To fix this, the relevant commits from the mfd tree could be put into a > "never to be rebased" branch (or separate git tree) and then this branch > merged into both the sound and mfd trees. Well, I don't think the codec register definitions don't have to be dependent on mfd tree at all. All other codec drivers have own definitions. Mark, can it be self-contained? thanks, Takashi -- 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/