linux-kernel - Re: [git pull] Fixes to 2.6.30rc2

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: <20090418.211643.248446717.davem@davemloft.net>
Date:	Sat, 18 Apr 2009 21:16:43 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	eric@...olt.net
Cc:	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
	airlied@...ux.ie
Subject: Re: [git pull] Fixes to 2.6.30rc2

From: Eric Anholt <eric@...olt.net>
Date: Sat, 18 Apr 2009 13:23:36 -0700

> On Sat, 2009-04-18 at 01:59 -0700, David Miller wrote:
>> Eric, any plans to ever push your work through David Airlie's DRM
>> tree?  I've been watching this for a few weeks and I'm mystified why
>> the Intel DRM drier stuff is so special that is always goes seperate.
>> 
>> It's seems foolish for David to manage the infrastructure and core DRM
>> changes, as well as those for radeon and the other drivers other than
>> Intel, which could potentially cause merge issues and conflicts with
>> your driver changes.
>> 
>> Why not do Intel DRM driver development via his tree?  I just don't
>> get it. :-/
> 
> Inside of the merge window, I am going through Dave again because he
> requested it (though delays meant that I didn't get a major cleanup in
> this merge window).  However, Dave is also quite busy, and not stealing
> his time every few days to pull my tree for just forwarding bugfixes on
> seems to be a win.

So you're essentially claiming that Dave isn't being a responsive
enough maintainer of the DRM subsystem?
--
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/