From: "Dave Airlie" <airlied@gmail.com>
To: "kernel list" <linux-kernel@vger.kernel.org>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
dri-devel <dri-devel@lists.sourceforge.net>,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: in-kernel DRM tree move around....
Date: Fri, 30 May 2008 16:26:38 +1000 [thread overview]
Message-ID: <21d7e9970805292326m1a238aa1id8b6733351ba15d3@mail.gmail.com> (raw)
In-Reply-To: <1212058935.26088.11.camel@shinybook.infradead.org>
On Thu, May 29, 2008 at 9:02 PM, David Woodhouse <dwmw2@infradead.org> wrote:
> On Thu, 2008-05-29 at 10:46 +1000, Dave Airlie wrote:
>> Hi,
>>
>> So I've been growing more annoyed with the current layout of the drm
>> tree in the kernel,
>>
>> a) it lives under char.
>> b) everything in one directory.
>> c) header files in one directory.
>> d) no header files exposed to userspace.
>>
>> http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=commitdiff;h=7df9a948d0f849466e3de259cccb49bc54cbad68
>>
>> is a proposal to create drivers/gpu/drm, (I may move AGP in there as
>> well later). It also creates per-driver subdirs.
>
> Looks sane from the header export POV. Passes headers_check and doesn't
> add any more instances of CONFIG_xxx visible to userspace (I'm coming
> after those, soon).
>
So assuming I fixed up the kbuild issues, any ideas on when it would
be a good plan to upstream this sorta major movement.
Not many DRM patches don't come via me, and I can fix up the ones that
do before I merge them.
Linus? any ideas on when you would prefer to take a tree like this?
start of rc1?
Dave.
next prev parent reply other threads:[~2008-05-30 6:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 0:46 Dave Airlie
2008-05-29 4:23 ` Sam Ravnborg
2008-05-29 5:23 ` Dave Airlie
2008-05-29 7:33 ` Sam Ravnborg
2008-05-29 8:20 ` Jan Engelhardt
2008-05-29 9:05 ` Alexander van Heukelum
2008-05-29 10:34 ` Alan Cox
2008-05-29 11:02 ` David Woodhouse
2008-05-30 6:26 ` Dave Airlie [this message]
2008-05-30 16:58 ` Jesse Barnes
2008-05-29 19:41 ` Eric Anholt
2008-06-01 14:57 ` Pavel Machek
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=21d7e9970805292326m1a238aa1id8b6733351ba15d3@mail.gmail.com \
--to=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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®