Date: Mon, 15 Mar 2004 15:26:21 -0800
From: Andrew Morton <akpm@osdl.org>
To: Ian Romanick <idr@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.sourceforge.net
Subject: Re: DRM reorganization
Message-Id: <20040315152621.43a5bcef.akpm@osdl.org>
In-Reply-To: <40562AEC.9080509@us.ibm.com>
References: <40562AEC.9080509@us.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1161
Lines: 24

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.
-
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/