linux-kernel - Re: linux-next: Tree for Dec 19

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:	Tue, 20 Dec 2011 14:20:48 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for Dec 19

Hi Mark,

On Tue, 20 Dec 2011 01:52:35 +0000 Mark Brown <broonie@...nsource.wolfsonmicro.com> wrote:
>
> On Mon, Dec 19, 2011 at 06:55:56PM +1100, Stephen Rothwell wrote:
> 
> > The regmap tree still has one build failure so I used the version of the
> > tree from next-20111214.
> 
> Please tell maintainers if you're doing this.  What is the issue here?
> The only thing I can think of is the broken GPIO driver that got merged
> some time ago without its dependencies which you were (much more sanely)
> flagging as broken.

Its 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").

Which I reported to you on Dec 15 (along with another build error in the
regulator tree that you have fixed).  You even created a patch to fix it
(Subject: [PATCH] mfd: Declare da9052_regmap_config for the bus drivers)
but that has not appeared in your tree yet.

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

Content of type "application/pgp-signature" skipped