linux-kernel - Re: [git pull] drm - fixes + radeon KMS (part 2)

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]

Message-ID: <21d7e9970906141943s8dd6e27sd4308413601d65e3@mail.gmail.com>
Date:	Mon, 15 Jun 2009 12:43:38 +1000
From:	Dave Airlie <airlied@...il.com>
To:	Greg KH <greg@...ah.com>
Cc:	Dave Airlie <airlied@...ux.ie>, torvalds@...ux-foundation.org,
	dri-devel@...ts.sf.net, linux-kernel@...r.kernel.org
Subject: Re: [git pull] drm - fixes + radeon KMS (part 2)

On Mon, Jun 15, 2009 at 12:22 PM, Greg KH<greg@...ah.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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/