On Mon, Jun 15, 2009 at 03:08:56AM +0100, Dave Airlie wrote:
> 
> Hi Linus,
> 
> Please pull the 'drm-linus' branch from
> ssh://master.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git drm-linus
> 
> This is big. It contains the initial TTM memory manager + ATI radeon KMS 
> support. Currently the KMS code is part of the DRM radeon driver however 
> it is very clearly separated internally from the old codepaths. We've 
> elected to keep the radeon KMS Kconfig build/enable under staging for now 
> since we may have some ABI tweaks to sort out in this release cycle, 
> however the code is all in the drm. I don't think this enables crap 
> tainting, but at least no-one will find kms by accident.

No, the module loader looks for stuff in drivers/staging/ to cause a
"taint".

But why not just keep the Kconfig stuff in your own directory, and
depend on CONFIG_STAGING if you want to not have it show up for "normal"
users?  It seems odd to put anything in drivers/staging/Kconfig for
something that is not in drivers/staging.

I'm guessing this Kconfig change was not in linux-next?  Or had it been
there and I just missed it somehow?

thanks,

greg k-h

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to