lkml.org 
[lkml]   [2013]   [Jan]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [PATCH 76/86] fs/btrfs: remove depends on CONFIG_EXPERIMENTAL
Date
On Wed, 16 Jan 2013 18:54:08 -0800
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.
>
> Cc: Chris Mason <chris.mason@fusionio.com>
> Cc: Al Viro <viro@zeniv.linux.org.uk>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Signed-off-by: Kees Cook <keescook@chromium.org>
> ---
> fs/btrfs/Kconfig | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/fs/btrfs/Kconfig b/fs/btrfs/Kconfig
> index d33f01c..ccd25ba 100644
> --- a/fs/btrfs/Kconfig
> +++ b/fs/btrfs/Kconfig
> @@ -1,6 +1,5 @@
> config BTRFS_FS
> - tristate "Btrfs filesystem (EXPERIMENTAL) Unstable disk
> format"
> - depends on EXPERIMENTAL
> + tristate "Btrfs filesystem Unstable disk format"

No longer an experiment but still "Unstable". But is it broken?
Or is it staging or a pet?
From my naive point of view it seems like this set of patches is
unleashing a bunch of bad stuff onto anyone that actually sets
CONFIG_EXPERIMENTAL "n". But I guess it's supposed to get caught in
linux-next.

> select LIBCRC32C
> select ZLIB_INFLATE
> select ZLIB_DEFLATE
> --
> 1.7.9.5
>


--




\
 
 \ /
  Last update: 2013-01-17 21:02    [W:0.387 / U:0.024 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site