On Mon, 23 Apr 2012 20:40:48 +0200, Wolfram Sang wrote: > 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 <w.sang@xxxxxxxxxxxxxx> > Cc: Lars-Peter Clausen <lars@xxxxxxxxxx> > Cc: Stephen Warren <swarren@xxxxxxxxxxxxx> > Cc: David Daney <ddaney.cavm@xxxxxxxxx> > Cc: Peter Korsgaard <jacmet@xxxxxxxxxx> > Cc: Guenter Roeck <guenter.roeck@xxxxxxxxxxxx> > Cc: Michael Lawnick <ml.lawnick@xxxxxx> > Cc: Jean Delvare <khali@xxxxxxxxxxxx> > --- > drivers/i2c/Kconfig | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/drivers/i2c/Kconfig b/drivers/i2c/Kconfig > index 5f13c62..5a3bb3d 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 Acked-by: Jean Delvare <khali@xxxxxxxxxxxx> -- Jean Delvare -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
