linux-kernel - Re: linux-next: build failure after merge of the regmap tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 15 Dec 2011 06:17:57 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	ashishj3 <ashish.jangam@...tcummins.com>,
	Grant Likely <grant.likely@...retlab.ca>,
	David Dajun Chen <dchen@...semi.com>
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/