From: Tony Breeds <tony@bakeyournoodle.com>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Quieten arch/powerpc in a allmodconfig build.
Date: Wed, 8 Apr 2009 15:51:26 +1000 [thread overview]
Message-ID: <20090408055126.GG16602@bilbo.ozlabs.org> (raw)
In-Reply-To: <1239167335.10104.26.camel@localhost>
On Wed, Apr 08, 2009 at 03:08:55PM +1000, Michael Ellerman wrote:
> The getter routines in here could really multiplex their return values
> with a negative error code, which I generally prefer, but this works I
> guess.
I was hoping someone would notice and suggest it. tag you're it!
> Do you need a new spacebar? :D
nowhydoyouask?
> This one is a bug surely?
Hmm actually I think you're right. I dont want to push my luck with the gcc
hackers though
> Gah, gcc sucks. It should just not warn in these cases where it doesn't
> know wth is going on.
I don't think you'll get any arguments. it only there was a -Wnowarnunused!
Yours Tony
next prev parent reply other threads:[~2009-04-08 5:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 4:36 [PATCH] Quieten arch/powerpc in a allmodconfig build Tony Breeds
2009-04-08 5:08 ` Michael Ellerman
2009-04-08 5:51 ` Tony Breeds [this message]
2009-04-08 6:13 ` Tony Breeds
2009-04-08 6:23 ` Michael Ellerman
2009-04-08 6:48 ` Michael Ellerman
2009-04-08 7:42 ` Geert Uytterhoeven
2009-04-08 18:47 ` Nathan Lynch
2009-04-09 0:01 ` Tony Breeds
2009-04-10 4:21 ` Nathan Lynch
2009-04-10 17:19 ` Segher Boessenkool
2009-04-09 22:46 ` Segher Boessenkool
2009-04-09 22:45 ` Tony Breeds
2009-04-09 23:11 ` Stephen Rothwell
2009-04-09 23:23 ` Segher Boessenkool
2009-04-10 18:03 ` Scott Wood
2009-04-10 18:35 ` Andreas Schwab
2009-04-10 18:43 ` Scott Wood
2009-04-10 20:28 ` Segher Boessenkool
2009-04-10 20:45 ` Segher Boessenkool
2009-04-10 21:51 ` Scott Wood
2009-04-09 23:18 ` Segher Boessenkool
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=20090408055126.GG16602@bilbo.ozlabs.org \
--to=tony@bakeyournoodle.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
/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).