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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120228120037.GD3683@opensource.wolfsonmicro.com>
Date:	Tue, 28 Feb 2012 12:00:37 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	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 04:58:57PM +1100, Stephen Rothwell wrote:

> Caused by commits ac8d91c80190 ("regmap: Supply ranges to the sync
> operations" and a0941e562e80 ("regmap: Fix x86_64 breakage") from the
> regmap tree interacting with commits "bitops: rename for_each_set_bit_cont()
> in favor of analogous list.h function" and "bitops: remove
> for_each_set_bit_cont()" from the akpm tree.

Oh, that explains what went wrong there!  I had thought that
for_each_set_bit_from() must be ARM-specific somehow when I saw your
report and didn't actually reexamime on ARM when fixing up as _cont was
in the header (admittedly I was in a rush doing the fixup).

> -	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?

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