From: "Alexander van Heukelum" <heukelum@fastmail.fm>
To: "Dave Airlie" <airlied@gmail.com>,
"kernel list" <linux-kernel@vger.kernel.org>,
"dri-devel" <dri-devel@lists.sourceforge.net>
Subject: Re: in-kernel DRM tree move around....
Date: Thu, 29 May 2008 11:05:08 +0200 [thread overview]
Message-ID: <1212051908.8215.1255644495@webmail.messagingengine.com> (raw)
In-Reply-To: <21d7e9970805281746k71b47ed2i79c06288d2dca022@mail.gmail.com>
On Thu, 29 May 2008 10:46:22 +1000, "Dave Airlie" <airlied@gmail.com>
said:
> 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 like a lot more suitable place! I just wonder if drivers/video/drm
would be even more logical?
Greetings,
Alexander
> This to me solves the a-d problems.
>
> There is also an out-of-tree kernel drm which I'll probably give some
> more thought later.
>
> Dave.
--
Alexander van Heukelum
heukelum@fastmail.fm
--
http://www.fastmail.fm - Does exactly what it says on the tin
next prev parent reply other threads:[~2008-05-29 9:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 0:46 in-kernel DRM tree move around 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 [this message]
2008-05-29 10:34 ` Alan Cox
2008-05-29 11:02 ` David Woodhouse
2008-05-30 6:26 ` Dave Airlie
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=1212051908.8215.1255644495@webmail.messagingengine.com \
--to=heukelum@fastmail.fm \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.sourceforge.net \
--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