DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=JFPxlDvJEKReTMeW0RLNlsDrqR8KrnQR+A8eHHXfCYA7UNhUFGFg238eLlR0o+Y55l
         FVCBm/jJQ9O4dd5SMX5Qa9ExIUWBiL1EAZ8lvdJhX3Hx4ggUUu9LHCL3stIKbh9a7N2I
         hM8OVn79luGxzxHn83yk4bS8sTQ8n8OxPqurU=
MIME-Version: 1.0
In-Reply-To: <20090615022235.GA12905@kroah.com>
References: <alpine.DEB.2.00.0906150302250.20307@skynet.skynet.ie>
	 <20090615022235.GA12905@kroah.com>
Date: Mon, 15 Jun 2009 12:43:38 +1000
Message-ID: <21d7e9970906141943s8dd6e27sd4308413601d65e3@mail.gmail.com>
Subject: Re: [git pull] drm - fixes + radeon KMS (part 2)
From: Dave Airlie <airlied@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Dave Airlie <airlied@linux.ie>, torvalds@linux-foundation.org,
       dri-devel@lists.sf.net, linux-kernel@vger.kernel.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1952
Lines: 47

On Mon, Jun 15, 2009 at 12:22 PM, Greg KH<greg@kroah.com> wrote:
> 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?
>

No since I was on holidays until the just before the merge window
opened, the patches
did get posted to lkml but missed your cc.

Well we'd like to make sure people go via the staging menus to get at
the kconfig option
for now, granted it probably doesn't matter whether it goes in staging
menus or in drm depends
on CONFIG_STAGING. Up to you I can post a patch after this merge to
move it to drm.

Since its only temporary I'm not hugely pushed about taint.

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