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 for Android: free password hash cracker in your pocket

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

Message-Id: <20120228140810.4cf9d477.akpm@linux-foundation.org>
Date:	Tue, 28 Feb 2012 14:08:10 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
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, 28 Feb 2012 12:00:37 +0000
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.
--
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/