Messages in this thread | | | Date | Mon, 4 Mar 2013 10:59:30 -0800 | Subject | Re: [PATCH] md/raid456: remove depends on CONFIG_EXPERIMENTAL | From | Kees Cook <> |
| |
On Tue, Feb 26, 2013 at 5:27 PM, Dan Williams <djbw@fb.com> wrote: > On Fri, Feb 22, 2013 at 11:40 PM, Kees Cook <keescook@chromium.org> wrote: >> The CONFIG_EXPERIMENTAL 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, remove it from any "depends on" lines in Kconfigs. >> >> Signed-off-by: Kees Cook <keescook@chromium.org> >> Cc: Arjan van de Ven <arjan@linux.intel.com> >> Cc: Dan Williams <dan.j.williams@intel.com> >> Cc: Alasdair G Kergon <agk@redhat.com> >> --- >> drivers/md/Kconfig | 1 - >> 1 file changed, 1 deletion(-) >> >> diff --git a/drivers/md/Kconfig b/drivers/md/Kconfig >> index 7cdf359..0cc3a3d 100644 >> --- a/drivers/md/Kconfig >> +++ b/drivers/md/Kconfig >> @@ -158,7 +158,6 @@ config MULTICORE_RAID456 >> bool "RAID-4/RAID-5/RAID-6 Multicore processing (EXPERIMENTAL)" >> depends on MD_RAID456 >> depends on SMP >> - depends on EXPERIMENTAL > > In this case MULTICORE_RAID456 and the related code should go as > well... now that there are patches to supersede this implementation in > md-next.
Can my original patch go through as-is for Linus's tree? Right now, this is the last use of EXPERIMENTAL in v3.9-rc1. If we can drop it, we can remove the config item entirely from v3.9.
-Kees
-- Kees Cook Chrome OS Security
| |