linux-kernel - Re: in-kernel DRM tree move around....

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 30 May 2008 09:58:53 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	dri-devel@...ts.sourceforge.net
Cc:	"Dave Airlie" <airlied@...il.com>,
	"kernel list" <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: in-kernel DRM tree move around....

On Thursday, May 29, 2008 11:26 pm Dave Airlie wrote:
> On Thu, May 29, 2008 at 9:02 PM, David Woodhouse <dwmw2@...radead.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=commitdi
> >>ff;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?

Yes please, as soon as the merge window opens.  Now if we could just convince 
you to host a full kernel tree for DRM development, with a separate, 
symlinked BSD dir at the top level, we'd be all set. :)

Jesse
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/