linux-kernel - linux-next: build failure after merge of the regulator 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>] [day] [month] [year] [list]

Message-Id: <20120410130135.662efa37bb9072cbe6ed5f21@canb.auug.org.au>
Date:	Tue, 10 Apr 2012 13:01:35 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Liam Girdwood <lrg@...com>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: linux-next: build failure after merge of the regulator tree

Hi all,

After merging the regulator tree, today's linux-next build (x86_64
allmodconfig) failed like this:

drivers/regulator/ab8500.c: In function 'ab8500_regulator_probe':
drivers/regulator/ab8500.c:783:9: error: invalid type argument of '->' (have 'struct regulator_config')
drivers/regulator/ab8500.c:784:9: error: invalid type argument of '->' (have 'struct regulator_config')
drivers/regulator/ab8500.c:785:9: error: invalid type argument of '->' (have 'struct regulator_config')

Caused by commit c172708d38a4 ("regulator: core: Use a struct to pass in
regulator runtime configuration").

I have used the regulator tree from next-20120405 for today.
-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

Content of type "application/pgp-signature" skipped