From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932313Ab1LOG1X (ORCPT ); Thu, 15 Dec 2011 01:27:23 -0500 Received: from tx2ehsobe002.messaging.microsoft.com ([65.55.88.12]:5628 "EHLO TX2EHSOBE003.bigfish.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932282Ab1LOG1T (ORCPT ); Thu, 15 Dec 2011 01:27:19 -0500 X-SpamScore: -15 X-BigFish: VPS-15(zz9371I542M1432N98dKzz1202hzzz2dh2a8h668h839h8e2h8e3h93fh61h) X-Spam-TCS-SCL: 0:0 X-Forefront-Antispam-Report: CIP:59.163.77.45;KIP:(null);UIP:(null);IPV:NLI;H:Outbound.kpitcummins.com;RD:59.163.77.45.static.vsnl.net.in;EFVD:NLI X-FB-SS: 0, From: Ashish Jangam To: Mark Brown , Stephen Rothwell CC: "linux-next@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Grant Likely , David Dajun Chen Subject: RE: linux-next: build failure after merge of the regmap tree Thread-Topic: linux-next: build failure after merge of the regmap tree Thread-Index: AQHMuvFJBFajYHNTuE6ZKBNQiG+z65Xcbhgg Date: Thu, 15 Dec 2011 06:24:44 +0000 Message-ID: References: <20111215170517.0b7fc08487881743ca76c192@canb.auug.org.au> <20111215061757.GC24287@sirena.org.uk> In-Reply-To: <20111215061757.GC24287@sirena.org.uk> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.10.38.22] Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 X-OriginatorOrg: kpitcummins.com Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by nfs id pBF6RUXT007067 > -----Original Message----- > From: Mark Brown [mailto:broonie@opensource.wolfsonmicro.com] > Sent: Thursday, December 15, 2011 11:48 AM > To: Stephen Rothwell > Cc: linux-next@vger.kernel.org; linux-kernel@vger.kernel.org; Ashish > Jangam; Grant Likely; David Dajun Chen > Subject: Re: linux-next: build failure after merge of the regmap tree > > On Thu, Dec 15, 2011 at 05:05:17PM +1100, Stephen Rothwell wrote: > > > drivers/gpio/gpio-da9052.c:25:35: fatal error: linux/mfd/da9052/gpio.h: > No such file or directory > > > So, it looks like this would never have built > > (include/linux/mfd/da9052/gpio.h never existed) but noone ever enabled > > CONFIG_PMIC_DA9052 before (which CONFIG_GPIO_DA9052 depends on). > > > drivers/gpio/gpio-da9052.c was added with commit 07bfc9152365 ("GPIO: > > DA9052 GPIO module v3") in v3.1-rc1. > > The issue here is that the GPIO driver was merged prior to review being > completed for the MFD and then problems with the MFD caused lots of > changes in the rest of the series. The MFD review is now fine so it's > been merged (via regmap due to use of new regmap features) but the GPIO > driver needs updating. > > Ashish or Daneil, could you please send a patch fixing this? Possibly > just a case of adding the new header. I have a fix for this issue will just take an incremental patch and post it. {.n++%ݶw{.n+{G{ayʇڙ,jfhz_(階ݢj"mG?&~iOzv^m ?I