public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Dave Airlie <airlied@linux.ie>
Cc: torvalds@linux-foundation.org, dri-devel@lists.sf.net,
	linux-kernel@vger.kernel.org
Subject: Re: [git pull] drm - fixes + radeon KMS (part 2)
Date: Sun, 14 Jun 2009 19:22:35 -0700	[thread overview]
Message-ID: <20090615022235.GA12905@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0906150302250.20307@skynet.skynet.ie>

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

  reply	other threads:[~2009-06-15  2:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-15  2:08 [git pull] drm - fixes + radeon KMS (part 2) Dave Airlie
2009-06-15  2:22 ` Greg KH [this message]
2009-06-15  2:43   ` Dave Airlie
2009-06-16 15:53     ` Ryan Hope
2009-06-16 18:20       ` Linus Torvalds
2009-06-16 20:45         ` Dave Airlie
2009-06-16 20:52           ` Linus Torvalds
2009-06-16 20:56             ` Dave Airlie
2009-06-16 21:03               ` Greg KH
2009-06-16 18:45     ` Greg KH

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=20090615022235.GA12905@kroah.com \
    --to=greg@kroah.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.sf.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