linux-kernel - Re: [git pull] drm fixes

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: <alpine.LFD.2.00.1006071057300.3515@i5.linux-foundation.org>
Date:	Mon, 7 Jun 2010 11:00:51 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Dave Airlie <airlied@...ux.ie>
cc:	dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Re: [git pull] drm fixes

On Mon, 7 Jun 2010, Dave Airlie wrote:
> 
> 3 regressions fixes, one radeon loading on IGP, one i865 loading, one and 
> an evergreen userspace interaction workaround.

This is:

	 26 files changed, 372 insertions(+), 66 deletions(-)

and there are apparently several reports of known problems (the problem 
with modesetting) that isn't even addressed.

See my -rc2 announcement. I absolutely do NOT want any new code. I want 
regression fixes, fixes for security issues, and fixes for oopses. Nothing 
else. I'm going to be hardassed about this, because quite frankly, if I'm 
not, people will just continue with the same-old, same-old, and send me 
random stuff without thinking hard about it.

So please. Just make me a tree that has regression fixes _only_. I'm not 
AT ALL interested in "it is useful to report the gpu temp". If it was so 
useful, and if it was ready before the merge window, it should hav gone in 
then. That clearly wasn't the case, so it's not going in now either.

		Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/