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 for Android: free password hash cracker in your pocket

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

Message-ID: <AANLkTimZWtOLiDT3KoUKZtsKfj4Aeu+XMF+rLc0wCSYk@mail.gmail.com>
Date:	Thu, 24 Mar 2011 07:37:36 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Ilija Hadzic <ihadzic@...earch.bell-labs.com>
Cc:	Dave Airlie <airlied@...il.com>,
	Michel Dänzer <michel@...nzer.net>,
	linux-kernel@...r.kernel.org,
	DRI mailing list <dri-devel@...ts.freedesktop.org>
Subject: Re: [git pull] drm fixes

On Thu, Mar 24, 2011 at 4:31 AM, Ilija Hadzic
<ihadzic@...earch.bell-labs.com> wrote:
>
> OK, I'll update libdrm side to match this change and send the patch later
> today

Quite frankly, this whole discussion is a clear example of why DRM has
been problematic.

Why the hell am I getting pushed stuff that is clearly not baked? It's
the second week of the merge window, the stuff I'm getting should have
been finalized two weeks ago, not be something that is still being
discussed and that has API issues.

In other words: Why should I pull this at all?

                      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/