All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Kevin Winchester <kjwinchester@gmail.com>
Cc: Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Bisecting tip/auto-x86-next?
Date: Fri, 20 Jun 2008 12:07:08 +0200	[thread overview]
Message-ID: <20080620100708.GC17692@elte.hu> (raw)
In-Reply-To: <485AFC9B.7090502@gmail.com>


* Kevin Winchester <kjwinchester@gmail.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

  parent reply	other threads:[~2008-06-20 10:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-20  0:40 Bisecting tip/auto-x86-next? Kevin Winchester
2008-06-20  7:15 ` Sitsofe Wheeler
2008-06-20 10:04 ` Ingo Molnar
2008-06-20 22:23   ` Kevin Winchester
2008-06-20 10:07 ` Ingo Molnar [this message]
2008-06-20 10:17 ` Ingo Molnar
2008-06-20 10:49   ` Pavel Machek
2008-06-20 11:40     ` Kevin Winchester
2008-06-20 10:51   ` Rafael J. Wysocki
2008-06-20 11:37   ` Kevin Winchester
2008-06-20 15:36     ` Ingo Molnar
2008-06-21  0:00       ` Kevin Winchester
2008-06-21  0:14         ` Yinghai Lu
2008-06-21 10:00           ` Kevin Winchester
2008-06-21 10:18             ` Yinghai Lu
2008-06-21 10:23               ` Kevin Winchester
2008-06-21 10:30                 ` Yinghai Lu
2008-06-21 10:39                   ` Kevin Winchester
2008-06-21 10:50                     ` Yinghai Lu
2008-06-21 11:49                       ` Kevin Winchester
2008-06-23 11:12                         ` Ingo Molnar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080620100708.GC17692@elte.hu \
    --to=mingo@elte.hu \
    --cc=hpa@zytor.com \
    --cc=kjwinchester@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.