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 <keesc...@chromium.org>
Cc: David S. Miller <da...@davemloft.net>
Cc: Asias He <as...@redhat.com>
Cc: Michael S. Tsirkin <m...@redhat.com>
---
drivers/vhost/Kconfig.blk | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/vhost/Kconfig.blk b/drivers/vhost/Kconfig.blk
index 831a121..eeffc8b 100644
--- a/drivers/vhost/Kconfig.blk
+++ b/drivers/vhost/Kconfig.blk
@@ -1,6 +1,6 @@
config VHOST_BLK
- tristate "Host kernel accelerator for virtio blk (EXPERIMENTAL)"
- depends on BLOCK && EXPERIMENTAL && EVENTFD && m
+ tristate "Host kernel accelerator for virtio blk"
+ depends on BLOCK && EVENTFD && m
---help---
This kernel module can be loaded in host kernel to accelerate
guest block with virtio_blk. Not to be confused with virtio_blk
--
1.7.9.5
--
Kees Cook
Chrome OS Security
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
