CAPI: Remove experimental tag from middleware feature
authorJan Kiszka <jan.kiszka@web.de>
Mon, 8 Feb 2010 10:12:45 +0000 (10:12 +0000)
committerDavid S. Miller <davem@davemloft.net>
Wed, 17 Feb 2010 00:01:36 +0000 (16:01 -0800)
Despite all its bugs, the middleware support of our CAPI stack was
already in use for many, many moons. And after going through its code,
fixing all issues I found, I feel it deserves to officially become a
non-experimental feature.

Signed-off-by: Jan Kiszka <jan.kiszka@web.de>
Signed-off-by: David S. Miller <davem@davemloft.net>
drivers/isdn/capi/Kconfig

index d607d465786ef7c28e42e64e4fcf8a8147bb6ae0..a168e8a891beac1b7975a169b2c7edec58623a4c 100644 (file)
@@ -17,8 +17,7 @@ config CAPI_TRACE
          If unsure, say Y.
 
 config ISDN_CAPI_MIDDLEWARE
-       bool "CAPI2.0 Middleware support (EXPERIMENTAL)"
-       depends on EXPERIMENTAL
+       bool "CAPI2.0 Middleware support"
        help
          This option will enhance the capabilities of the /dev/capi20
          interface.  It will provide a means of moving a data connection,