Messages in this thread | | | Date | Mon, 15 Mar 2004 16:31:31 -0800 | From | Andrew Morton <> | Subject | Re: [Dri-devel] Re: DRM reorganization |
| |
Ian Romanick <idr@us.ibm.com> wrote: > > >>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. :)
Oh. So what was the question again?
As far as I know, there's nobody in DRI-land who actually prepares and sends patches. Fixing that would be a good first step ;)
I've had a 130k DRM patch in -mm since February 8th. Presumably it's out of date. As far as I know nobody is pushing more recent patches upstream.
What's the process here, and who should I be dealing with?
Thanks. - 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/
| |