From: Alex Deucher <agd5f@yahoo.com>
To: Andrew Morton <akpm@osdl.org>, Ian Romanick <idr@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.sourceforge.net
Subject: Re: [Dri-devel] Re: DRM reorganization
Date: Mon, 15 Mar 2004 15:51:25 -0800 (PST) [thread overview]
Message-ID: <20040315235125.96790.qmail@web11305.mail.yahoo.com> (raw)
In-Reply-To: <20040315152621.43a5bcef.akpm@osdl.org>
--- Andrew Morton <akpm@osdl.org> wrote:
> Ian Romanick <idr@us.ibm.com> wrote:
> >
> > 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?
>
> - Make sure that the files in the main kernel distribution are up to
> date.
>
> - Prepare a shell script which does all the relevant file moves, send
> to
> Linus, along with a diff which fixes up Kconfig and Makefiles.
>
> - Start patching the files in their new locations.
>
>
we (as dri developers) should probably also sync the other way more
regularly too. sometimes there are changes in the kernel tree that
don't get back to the dri/drm tree in a timely manner.
Alex
__________________________________
Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam
http://mail.yahoo.com
next prev parent reply other threads:[~2004-03-15 23:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 22:15 Ian Romanick
2004-03-15 23:26 ` Andrew Morton
2004-03-15 23:51 ` Alex Deucher [this message]
2004-03-16 0:15 ` [Dri-devel] " 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=20040315235125.96790.qmail@web11305.mail.yahoo.com \
--to=agd5f@yahoo.com \
--cc=akpm@osdl.org \
--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 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®