linux-kernel - Re: [PATCH] x86: Change x86 to use generic find_next

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: <20080309201152.GB28454@elte.hu>
Date:	Sun, 9 Mar 2008 21:11:52 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Alexander van Heukelum <heukelum@...lshack.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	LKML <linux-kernel@...r.kernel.org>, heukelum@...tmail.fm
Subject: Re: [PATCH] x86: Change x86 to use generic find_next_bit


* Alexander van Heukelum <heukelum@...lshack.com> wrote:

> --- a/lib/find_next_bit.c
> +++ b/lib/find_next_bit.c
> @@ -15,6 +15,8 @@
>  #include <asm/byteorder.h>
>  
>  #define BITOP_WORD(nr)		((nr) / BITS_PER_LONG)
> +#undef find_next_bit
> +#undef find_next_zero_bit

this bit looks weird - did you need it for testing?

	Ingo
--
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/