From: Andi Kleen <andi@firstfloor.org>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>
Subject: Re: warning from gcc version 4.6.0 20100416
Date: Fri, 11 Jun 2010 08:16:10 +0200 [thread overview]
Message-ID: <20100611061610.GA6864@basil.fritz.box> (raw)
In-Reply-To: <4C11A598.8090504@gmail.com>
On Thu, Jun 10, 2010 at 07:55:20PM -0700, Justin P. Mattock wrote:
> o.k. andi,
>
> here is the rest of the warnings that
> I see when compiling the kernel
>
> I can try and create some patches for
> this(hopefully!!)
The key point is that you need to review
each warning if it's a real bug or just a false
positive.
This is not always trivial, I got at least one
wrong in the earlier series (shut up one real bug)
-Andi
next prev parent reply other threads:[~2010-06-11 6:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 2:55 warning from gcc version 4.6.0 20100416 Justin P. Mattock
2010-06-11 6:16 ` Andi Kleen [this message]
2010-06-11 6:34 ` Justin P. Mattock
2010-06-14 1:17 ` Bill Davidsen
2010-06-14 2:54 ` Justin P. Mattock
2010-06-14 7:49 ` Andi Kleen
2010-06-14 14:51 ` Bill Davidsen
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=20100611061610.GA6864@basil.fritz.box \
--to=andi@firstfloor.org \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).