mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Airlie <airlied@gmail.com>
To: Eric Anholt <eric@anholt.net>
Cc: David Miller <davem@davemloft.net>,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [git pull] Fixes to 2.6.30rc2
Date: Sun, 19 Apr 2009 16:47:30 +1000	[thread overview]
Message-ID: <21d7e9970904182347m1dbb611dp3a71f16b0fd82bb7@mail.gmail.com> (raw)
In-Reply-To: <1240086216.11172.2954.camel@gaiman.anholt.net>

On Sun, Apr 19, 2009 at 6:23 AM, Eric Anholt <eric@anholt.net> wrote:
> On Sat, 2009-04-18 at 01:59 -0700, David Miller wrote:
>> From: Eric Anholt <eric@anholt.net>
>> Date: Fri, 17 Apr 2009 13:49:59 -0700
>>
>> >   git://git.kernel.org/pub/scm/linux/kernel/git/anholt/drm-intel drm-intel-next
>>
>> 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.

btw which cleanup, I seem to remember it arriving after the merge
window had opened.

The theory is the code was in my tree before Linus opened the window
or it doesn't
get merged.

Dave.

>
> --
> Eric Anholt
> eric@anholt.net                         eric.anholt@intel.com
>
>
>

  parent reply	other threads:[~2009-04-19  6:47 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
2009-04-19  6:34       ` Dave Airlie
2009-04-19  6:47     ` Dave Airlie [this message]
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=21d7e9970904182347m1dbb611dp3a71f16b0fd82bb7@mail.gmail.com \
    --to=airlied@gmail.com \
    --cc=davem@davemloft.net \
    --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®