From: Wolfram Sang Date: Mon, 23 Apr 2012 18:31:18 +0000 (+0200) Subject: i2c: muxes are not EXPERIMENTAL anymore X-Git-Tag: firefly_0821_release~3680^2~2744^2~11 X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=951eef3955117cfaf3eafea601bf06ba2090ca0f;p=firefly-linux-kernel-4.4.55.git i2c: muxes are not EXPERIMENTAL anymore We got multiple patches to add mux support to device tree, so people are using it happily already and build up on it. I also used it in a project without encountering problems. 20 months of EXPERIMENTAL should do for this. Signed-off-by: Wolfram Sang Acked-by: Peter Korsgaard Acked-by: Guenter Roeck Acked-by: Jean Delvare Acked-by: Stephen Warren Acked-by: Michael Lawnick Cc: Lars-Peter Clausen Cc: David Daney --- diff --git a/drivers/i2c/Kconfig b/drivers/i2c/Kconfig index 5f13c62e64b4..5a3bb3d738d8 100644 --- a/drivers/i2c/Kconfig +++ b/drivers/i2c/Kconfig @@ -49,7 +49,6 @@ config I2C_CHARDEV config I2C_MUX tristate "I2C bus multiplexing support" - depends on EXPERIMENTAL help Say Y here if you want the I2C core to support the ability to handle multiplexed I2C bus topologies, by presenting each