linux-kernel - Re: kms in defconfig

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:	Tue, 28 Apr 2009 10:45:06 +0900
From:	Tejun Heo <tj@...nel.org>
To:	Dave Airlie <airlied@...il.com>
CC:	Ingo Molnar <mingo@...e.hu>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: kms in defconfig

Hello,

Dave Airlie wrote:
> My main worry is distro configs going forward, where they pull
> something from defconfig, granted I've no idea if that'll happen,
> maybe distro kernel maintainers are smarter than I give them credit
> for :-)

We're probably as dumb as or even dumber than you give credit for but
we do have testing cycles in place to compensate for it, so I don't
think distros-might-screw-up needs to be a concern when deciding what
gets turned on in defconfig.  :-)

I think defconfig should enable options such that it shows where
upstream kernel is headed, so FWIW +1 for KMS from me.

Thanks.

-- 
tejun
--
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/