From: Keith Whitwell <keith@tungstengraphics.com>
To: Ian Romanick <idr@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
"DRI developer's list" <dri-devel@lists.sourceforge.net>
Subject: Re: DRM code reorganization
Date: Tue, 03 Aug 2004 17:49:48 +0100 [thread overview]
Message-ID: <410FC22C.8030802@tungstengraphics.com> (raw)
In-Reply-To: <410FBD47.2060605@us.ibm.com>
Ian Romanick wrote:
> Keith Whitwell wrote:
>
>> We've actually managed to do a fair bit of cleanup already - if you
>> look at the gamma driver, there's a lot of stuff in there which used
>> to be shared but ifdef'ed out between all the drivers. The
>> __HAVE_MULTIPLE_DMA_QUEUES macro is a remnant of this, but I think
>> you'll break gamma when you try & remove it.
>
>
> It looks like __HAVE_MULTIPLE_DMA_QUEUES is a superset of
> __HAVE_DMA_QUEUE. My thinking was that the code for those two options
> could be merged. Does that seem reasonable?
If it looks reasonable in the codebase, I don't know any reason not to.
Keith
next prev parent reply other threads:[~2004-08-03 16:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 15:53 DRM code reorganization Jon Smirl
2004-08-02 18:02 ` Ian Romanick
2004-08-02 18:27 ` Keith Whitwell
2004-08-02 18:57 ` Dave Jones
2004-08-02 18:16 ` Alan Cox
2004-08-02 20:11 ` Ian Romanick
2004-08-02 20:42 ` Jon Smirl
2004-08-02 21:09 ` Dave Jones
2004-08-02 21:51 ` Michel Dänzer
2004-08-02 23:09 ` Jon Smirl
2004-08-02 23:24 ` Alan Cox
2004-08-02 20:45 ` Dave Jones
2004-08-02 23:53 ` Ian Romanick
2004-08-03 7:52 ` Keith Whitwell
2004-08-03 16:28 ` Ian Romanick
2004-08-03 16:49 ` Keith Whitwell [this message]
2004-08-03 0:06 ` Dave Airlie
2004-08-03 6:13 ` Eric Anholt
2004-08-02 23:48 ` Dave Airlie
2004-08-02 23:26 ` Alan Cox
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=410FC22C.8030802@tungstengraphics.com \
--to=keith@tungstengraphics.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=idr@us.ibm.com \
--cc=linux-kernel@vger.kernel.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.