mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: eric@anholt.net
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	airlied@linux.ie
Subject: Re: [git pull] Fixes to 2.6.30rc2
Date: Sat, 18 Apr 2009 21:16:43 -0700 (PDT)	[thread overview]
Message-ID: <20090418.211643.248446717.davem@davemloft.net> (raw)
In-Reply-To: <1240086216.11172.2954.camel@gaiman.anholt.net>

From: Eric Anholt <eric@anholt.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?

  reply	other threads:[~2009-04-19  4:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-17 20:49 Eric Anholt
2009-04-18  8:59 ` David Miller
2009-04-18 20:23   ` Eric Anholt
2009-04-19  4:16     ` David Miller [this message]
2009-04-19  6:34       ` Dave Airlie
2009-04-19  6:47     ` Dave Airlie
2009-04-20  6:00       ` Eric Anholt

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=20090418.211643.248446717.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=airlied@linux.ie \
    --cc=eric@anholt.net \
    --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®