All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Romanick <idr@us.ibm.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Dave Airlie <airlied@linux.ie>, linux-kernel@vger.kernel.org
Subject: Re: [BK pull] DRM macro removal tree
Date: Fri, 03 Sep 2004 11:46:43 -0700	[thread overview]
Message-ID: <4138BC13.2080005@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0409031100130.26393@ppc970.osdl.org>

Linus Torvalds wrote:
> On Fri, 3 Sep 2004, Dave Airlie wrote:
> 
>>This isn't the standard drm-2.6 tree, it is a separate tree for feeding
>>the macro removal function table stuff. The highlights of this tree are:
> 
> Hey, looks much cleaner, but I just wanted to check that this is all stuff
> that has been agreed upon in the DRM groups? I don't follow the DRM
> mailing list actively any more..

Yes, it is.  The general consensus is that all the other DRM / DRI 
developers are glad Dave is doing this work...so that we don't have to. :)

  reply	other threads:[~2004-09-03 18:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-03 10:37 [BK pull] DRM macro removal tree Dave Airlie
2004-09-03 18:01 ` Linus Torvalds
2004-09-03 18:46   ` Ian Romanick [this message]
2004-09-03 23:16   ` Dave Airlie

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=4138BC13.2080005@us.ibm.com \
    --to=idr@us.ibm.com \
    --cc=airlied@linux.ie \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.