Messages in this thread | | | Date | Wed, 3 Oct 2012 16:33:21 -0700 | Subject | Re: make CONFIG_EXPERIMENTAL invisible and default | From | Kees Cook <> |
| |
On Wed, Oct 3, 2012 at 4:29 PM, Guenter Roeck <linux@roeck-us.net> wrote: > On Tue, Oct 02, 2012 at 07:50:42PM -0000, Kees Cook wrote: >> This config item has not carried much meaning for a while now and is >> almost always enabled by default. As agreed during the Linux kernel >> summit, it should be removed. As a first step, remove it from being >> listed, and default it to on. Once it has been removed from all >> subsystem Kconfigs, it will be dropped entirely. >> >> CC: Greg KH <gregkh@linuxfoundation.org> >> CC: "Eric W. Biederman" <ebiederm@xmission.com> >> CC: Serge Hallyn <serge.hallyn@canonical.com> >> CC: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> >> CC: Andrew Morton <akpm@linux-foundation.org> >> CC: Frederic Weisbecker <fweisbec@gmail.com> >> Signed-off-by: Kees Cook <keescook@chromium.org> >> Acked-by: Serge Hallyn <serge.hallyn@canonical.com> >> >> --- >> This is the first of a series of 202 patches removing EXPERIMENTAL from >> all the Kconfigs in the tree. Should I send them all to lkml (with all >> the associated CCs), or do people want to cherry-pick changes from my >> tree? I don't want to needlessly flood the list. >> >> http://git.kernel.org/?p=linux/kernel/git/kees/linux.git;a=shortlog;h=refs/heads/experimental >> > I cherry-picked the hwmon/pmbus patch (commit 41c5b6bb).
Great, thanks!
-Kees
-- Kees Cook Chrome OS Security
| |