linux-kernel - Re: Bisecting tip/auto-x86-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 for Android: free password hash cracker in your pocket

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

Message-ID: <20080620100708.GC17692@elte.hu>
Date:	Fri, 20 Jun 2008 12:07:08 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Kevin Winchester <kjwinchester@...il.com>
Cc:	Ingo Molnar <mingo@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Bisecting tip/auto-x86-next?


* Kevin Winchester <kjwinchester@...il.com> wrote:

> include/asm/thread_info_64.h: In function ‘set_restore_sigmask’:
> include/asm/thread_info_64.h:189: warning: passing argument 2 of  
> ‘set_bit’ from incompatible pointer type
>
> -----------------
>
> Can I ignore these warnings and keep building the kernel anyway? [...]

btw., you can probably ignore this one safely. Also please tell me at 
which commit ID you were at when you triggered this warning.

	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/