dropping CONFIG_EXPERIMENTAL (was: warning: (BLK_DEV_RBD && CEPH_FS) selects CEPH_LIB which has unmet direct dependencies (NET && INET && EXPERIMENTAL))

dropping CONFIG_EXPERIMENTAL (was: warning: (BLK_DEV_RBD && CEPH_FS) selects CEPH_LIB which has unmet direct dependencies (NET && INET && EXPERIMENTAL))

[Kees Cook]

It looks like the drop-experimental patches have started to land in
Linus's tree ahead of schedule (they're queuing up in linux-next[1]
currently). These types of warnings don't happen if the first patch
from my series (that explicitly enables CONFIG_EXPERIMENTAL until all
references are removed) is in the tree.

How would people like to handle this? I could ask Linus to pull the
ceph change to make this specific warning go away, but I'm nervous
that we'll just continue to see one-off problems.

-Kees

[1] http://git.kernel.org/?p=linux/kernel/git/kees/linux.git;a=shortlog;h=refs/heads/linux-next

On Thu, Nov 1, 2012 at 11:27 AM, kbuild test robot
<fengguang.wu@intel.com> wrote:
> tree:   git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux master
> head:   8c23f406c6d86808726ace580657186bc3b44587
> commit: b8977285ecb0033b0bd9a99d4355f9c0bc8708f1 drivers/block: remove CONFIG_EXPERIMENTAL
> date:   9 days ago
> config: i386-randconfig-b610 (attached as .config)
>
> All warnings:
>
> warning: (BLK_DEV_RBD && CEPH_FS) selects CEPH_LIB which has unmet direct dependencies (NET && INET && EXPERIMENTAL)
> warning: (BLK_DEV_RBD && CEPH_FS) selects CEPH_LIB which has unmet direct dependencies (NET && INET && EXPERIMENTAL)
>
> ---
> 0-DAY kernel build testing backend         Open Source Technology Center
> Fengguang Wu, Yuanhan Liu                              Intel Corporation



-- 
Kees Cook
Chrome OS Security