Message-ID: <20040315235125.96790.qmail@web11305.mail.yahoo.com>
Date: Mon, 15 Mar 2004 15:51:25 -0800 (PST)
From: Alex Deucher <agd5f@yahoo.com>
Subject: Re: [Dri-devel] Re: DRM reorganization
To: Andrew Morton <akpm@osdl.org>, Ian Romanick <idr@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.sourceforge.net
In-Reply-To: <20040315152621.43a5bcef.akpm@osdl.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1587
Lines: 47


--- 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/