[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20111215171752.db0b6732fb591a91ef8c790a@canb.auug.org.au>
Date: Thu, 15 Dec 2011 17:17:52 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc: linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Liam Girdwood <lrg@...mlogic.co.uk>,
Ashish Jangam <ashish.jangam@...tcummins.com>,
David Dajun Chen <dchen@...semi.com>,
Samuel Ortiz <sameo@...ux.intel.com>
Subject: linux-next: build failure after merge of the regmap tree
Hi Mark,
After merging the regmap tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/mfd/da9052-spi.c: In function 'da9052_spi_probe':
drivers/mfd/da9052-spi.c:42:2: error: 'da9052_regmap_config' undeclared (first use in this function)
Caused by commit cfe04478fa1b ("MFD: DA9052/53 MFD core module add SPI
support v2"). Really, was this ever build tested?
da9052_regmap_config is defined in drivers/mfd/da9052-core.c but not
declared in any header file.
drivers/regulator/da9052-regulator.c: In function 'da9052_regulator_probe':
drivers/regulator/da9052-regulator.c:550:11: error: too few arguments to function 'regulator_register'
include/linux/regulator/driver.h:215:23: note: declared here
Caused by commit 08bf1c0ae97f ("regulator: DA9052/53 Regulator support")
from the regulator tree interacting with commit 2c043bcbf287 ("regulator:
pass additional of_node to regulator_register()") also from the regulator
tree. Again, building the above file depends on CONFIG_PMIC_DA9052 which
noone ever set before.
I have used the regmap tree from next-20111214 for today.
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists