From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [git pull] drm for 2.6.35-rc1 (revised)
Date: Sat, 22 May 2010 12:00:03 +1000 [thread overview]
Message-ID: <20100522120003.ee53af22.sfr@canb.auug.org.au> (raw)
In-Reply-To: <alpine.LFD.2.00.1005211154120.3689@i5.linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 947 bytes --]
Hi Linus,
On Fri, 21 May 2010 11:56:39 -0700 (PDT) Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
> I suspect we should have some "new warnings are errors" thing for
> linux-next, so that people can't do this.
I do attempt to report new warnings but they are often hard to spot among
all the "may be used uninitialised" rubbish of an X86_64 allmodconfig
build. Also, sometimes people ignore me, of course. :-(
That being said, I did not get the mentioned warning for either an i386
or x86_64 allmodconfig build - I wonder why not? Compiler differences?
Config differences? (See
http://kisskb.ellerman.id.au/kisskb/buildresult/2617918/ and
http://kisskb.ellerman.id.au/kisskb/buildresult/2617928/).
Ah, I did get it for an i386 defconfig build
(http://kisskb.ellerman.id.au/kisskb/buildresult/2617930/).
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-05-22 2:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 2:19 [git pull] drm tree for 2.6.35-rc1 Dave Airlie
2010-05-21 6:24 ` [git pull] drm for 2.6.35-rc1 (revised) Dave Airlie
2010-05-21 18:56 ` Linus Torvalds
2010-05-21 19:44 ` Randy Dunlap
2010-05-22 2:00 ` Stephen Rothwell [this message]
2010-05-22 2:03 ` Linus Torvalds
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=20100522120003.ee53af22.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®