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

Date:	Wed, 29 Feb 2012 10:13:13 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Akinobu Mita <akinobu.mita@...il.com>
Subject: Re: linux-next: build failure after merge of the akpm tree

On Tue, Feb 28, 2012 at 02:08:10PM -0800, Andrew Morton wrote:
> Mark Brown <broonie@...nsource.wolfsonmicro.com> wrote:

> > > -	for_each_set_bit_cont(i, lzo_blocks[0]->sync_bmp,
> > > +	for_each_set_bit_from(i, lzo_blocks[0]->sync_bmp,

> > That looks about right, yes.  Not sure what the best way to handle this
> > is, perhaps maintain _cont() for a while?

> I don't think that will be needed - for_each_set_bit_cont() only had
> two callers, both in arch/x86/kernel/cpu/perf_event.c.

Well, by "a while" I mostly mean "until after the merge window when the
new API is available".

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)