mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: [Dri-devel] Re: DRM reorganization
Date: Mon, 15 Mar 2004 16:31:31 -0800	[thread overview]
Message-ID: <20040315163131.1b03b49f.akpm@osdl.org> (raw)
In-Reply-To: <40564723.4010105@us.ibm.com>

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.

  reply	other threads:[~2004-03-16  0:34 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   ` [Dri-devel] " Alex Deucher
2004-03-16  0:15   ` Ian Romanick
2004-03-16  0:31     ` Andrew Morton [this message]
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=20040315163131.1b03b49f.akpm@osdl.org \
    --to=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®