From: Ian Romanick <idr@us.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.sourceforge.net
Subject: Re: [Dri-devel] Re: DRM reorganization
Date: Mon, 15 Mar 2004 16:15:31 -0800 [thread overview]
Message-ID: <40564723.4010105@us.ibm.com> (raw)
In-Reply-To: <20040315152621.43a5bcef.akpm@osdl.org>
Andrew Morton 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.
I'm not 100% sure what you mean. Right now the files in our CVS are
split between two directories. There's a "common" directory, which is
used on both Linux & BSD, and a Linux-specific directory. Our intention
is to shift around where some of the files are in our CVS. I don't
think we intend to move where things are in the Linux source tree.
That's part of why I'm asking. From talking to Linus in the past, I
know that merging in changes is a PITA due to our funky directory
structure. I'd like to make that easier. :)
next prev parent reply other threads:[~2004-03-16 0:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 22:15 DRM reorganization Ian Romanick
2004-03-15 23:26 ` Andrew Morton
2004-03-15 23:51 ` [Dri-devel] " Alex Deucher
2004-03-16 0:15 ` Ian Romanick [this message]
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=40564723.4010105@us.ibm.com \
--to=idr@us.ibm.com \
--cc=akpm@osdl.org \
--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 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.