From: Ian Romanick <idr@us.ibm.com>
To: linux-kernel@vger.kernel.org,
"DRI developer's list" <dri-devel@lists.sourceforge.net>
Subject: DRM reorganization
Date: Mon, 15 Mar 2004 14:15:08 -0800 [thread overview]
Message-ID: <40562AEC.9080509@us.ibm.com> (raw)
We're looking at reorganizing the way DRM drivers are maintained.
Currently, the DRM kernel code lives deep in a subdirectory of the DRI
tree (which is a partial copy of the XFree86 tree). We plan to move it
"up" to its own module at the top level. That should make it *much*
easier for people that want to do things with the DRM but don't want all
the rest of X (i.e., DRI w/DirectFB, etc.).
When we do this move, we're open to the possibility of reorganizing the
file structure. What can we do to make it easier for kernel release
maintainers to merge changes into their trees?
This is cross-posted to LKML & dri-devel, and I'm not on LKML. If you
reply, please hit the 'Reply to all' button. :)
next reply other threads:[~2004-03-15 22:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 22:15 Ian Romanick [this message]
2004-03-15 23:26 ` DRM reorganization Andrew Morton
2004-03-15 23:51 ` [Dri-devel] " Alex Deucher
2004-03-16 0:15 ` Ian Romanick
2004-03-16 0:31 ` Andrew Morton
2004-03-16 19:21 ` Dave Jones
2004-03-16 0:42 ` Jon Smirl
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=40562AEC.9080509@us.ibm.com \
--to=idr@us.ibm.com \
--cc=dri-devel@lists.sourceforge.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox