IPoIB/cm: Connected mode is no longer EXPERIMENTAL

Connected mode is now tested and used by lots of people.  No need to
hide it under CONFIG_EXPERIMENTAL.

Signed-off-by: Roland Dreier <rolandd@cisco.com>

diff --git a/drivers/infiniband/ulp/ipoib/Kconfig b/drivers/infiniband/ulp/ipoib/Kconfig
index 691525cf394a34f4b2e4f68bf9ee5ee0f6b1cb85..ccc7180818a30c034f39686afd5219b03093cdfa 100644 (file)
--- a/drivers/infiniband/ulp/ipoib/Kconfig
+++ b/drivers/infiniband/ulp/ipoib/Kconfig
@@ -11,16 +11,17 @@ config INFINIBAND_IPOIB
 
 config INFINIBAND_IPOIB_CM
        bool "IP-over-InfiniBand Connected Mode support"
-       depends on INFINIBAND_IPOIB && EXPERIMENTAL
+       depends on INFINIBAND_IPOIB
        default n
        ---help---
-         This option enables experimental support for IPoIB connected mode.
-         After enabling this option, you need to switch to connected mode through
-         /sys/class/net/ibXXX/mode to actually create connections, and then increase
-         the interface MTU with e.g. ifconfig ib0 mtu 65520.
+         This option enables support for IPoIB connected mode.  After
+         enabling this option, you need to switch to connected mode
+         through /sys/class/net/ibXXX/mode to actually create
+         connections, and then increase the interface MTU with
+         e.g. ifconfig ib0 mtu 65520.
 
-         WARNING: Enabling connected mode will trigger some
-         packet drops for multicast and UD mode traffic from this interface,
+         WARNING: Enabling connected mode will trigger some packet
+         drops for multicast and UD mode traffic from this interface,
          unless you limit mtu for these destinations to 2044.
 
 config INFINIBAND_IPOIB_DEBUG