Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751663Ab0LNFKY (ORCPT ); Tue, 14 Dec 2010 00:10:24 -0500 Received: from mail-yw0-f46.google.com ([209.85.213.46]:43239 "EHLO mail-yw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751005Ab0LNFKW convert rfc822-to-8bit (ORCPT ); Tue, 14 Dec 2010 00:10:22 -0500 MIME-Version: 1.0 In-Reply-To: <20101214154933.a4b36f69.sfr@canb.auug.org.au> References: <20101214154933.a4b36f69.sfr@canb.auug.org.au> Date: Tue, 14 Dec 2010 13:10:20 +0800 Message-ID: Subject: Re: linux-next: build failure after merge of the voltage tree From: Yong Shen To: Stephen Rothwell Cc: Liam Girdwood , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1287 Lines: 34 Hi Stephen, I had already noticed Liam. Mc13892's patch depends on other two patches which are not applied yet. Yong On Tue, Dec 14, 2010 at 12:49 PM, Stephen Rothwell wrote: > Hi Liam, > > After merging the voltage tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/regulator/mc13892-regulator.c:21:21: error: mc13xxx.h: No such file or directory > drivers/regulator/mc13892-regulator.c:261: error: array type has incomplete element type > drivers/regulator/mc13892-regulator.c:262: error: implicit declaration of function 'MC13xxx_DEFINE' > drivers/regulator/mc13892-regulator.c:262: error: 'MC13892_' undeclared here (not in a function) > > and on and on .... > > Caused by commit b0e2417cdbc12b1649245315a607ae8f1072b2bf ("regulator: > support PMIC mc13892"). ?A file missing from the commit, I assume. > > I have used the voltage tree form next-20101213 for today. > -- > Cheers, > Stephen Rothwell ? ? ? ? ? ? ? ? ? ?sfr@canb.auug.org.au > http://www.canb.auug.org.au/~sfr/ > -- 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/