[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <C3AE124F08223B42BC95AEB82F0F6CED1F9D0855@KCHJEXMB01.kpit.com>
Date: Thu, 15 Dec 2011 06:24:44 +0000
From: Ashish Jangam <Ashish.Jangam@...tcummins.com>
To: Mark Brown <broonie@...nsource.wolfsonmicro.com>,
Stephen Rothwell <sfr@...b.auug.org.au>
CC: "linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Grant Likely <grant.likely@...retlab.ca>,
David Dajun Chen <dchen@...semi.com>
Subject: RE: linux-next: build failure after merge of the regmap tree
> -----Original Message-----
> From: Mark Brown [mailto:broonie@...nsource.wolfsonmicro.com]
> Sent: Thursday, December 15, 2011 11:48 AM
> To: Stephen Rothwell
> Cc: linux-next@...r.kernel.org; linux-kernel@...r.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.
Powered by blists - more mailing lists