linux-kernel - Re: linux-next: build failure after merge of the mfd 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 for Android: free password hash cracker in your pocket

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

Date:	Fri, 18 May 2012 10:39:19 +0200
From:	Samuel Ortiz <sameo@...ux.intel.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Subject: Re: linux-next: build failure after merge of the mfd tree

Hi Stephen,

On Wed, May 16, 2012 at 04:09:06PM +1000, Stephen Rothwell wrote:
> Hi Samuel,
> 
> After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
> 
> drivers/built-in.o: In function `wm8400_i2c_probe':
> wm8400-core.c:(.text+0x100165): undefined reference to `devm_regmap_init_i2c'
> drivers/built-in.o: In function `wm8400_module_init':
> wm8400-core.c:(.init.text+0xb43c): undefined reference to `i2c_register_driver'
> drivers/built-in.o: In function `wm8400_module_exit':
> wm8400-core.c:(.exit.text+0x655): undefined reference to `i2c_del_driver'
> 
> Probably caused by commit 96cd102ae039 ("mfd: Don't support non-modular
> wm8400 build") which was introduced to fix other problems.  In this
> build, CONFIG_I2C=m and CONFIG_REGMAP_I2C=m.
> 
> I have used the mfd tree from next-20120511 again for today.
Sorry for the delay, this should be fixed now.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/
--
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/