linux-kernel - Re: [git pull] drm for 2.6.35-rc1 (revised)

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <20100522120003.ee53af22.sfr@canb.auug.org.au>
Date:	Sat, 22 May 2010 12:00:03 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Dave Airlie <airlied@...ux.ie>, linux-kernel@...r.kernel.org,
	dri-devel@...ts.freedesktop.org
Subject: Re: [git pull] drm for 2.6.35-rc1 (revised)

Hi Linus,

On Fri, 21 May 2010 11:56:39 -0700 (PDT) Linus Torvalds <torvalds@...ux-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@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped