Hi Benjamin, On Fri, 21 Jul 2017 11:37:59 +0200, Benjamin Tissoires wrote: > On Jul 20 2017 or thereabouts, Phil Reid wrote: > > On 20/07/2017 02:30, kbuild test robot wrote: > > > > > > > I understand how this is occurring. > > I2C=y, OF=y and I2C_PARPORT=m > > I2C_PARPORT selects I2C_SMBUS setting it to m > > > > Calling a function in i2c-smbus (module) from i2c-core (builtin) is then a problem. > > > > However there doesn't seem to be a way (that I can see) to have select statement force I2C_SMBUS=y if I2C=y > > What if I2C selects I2C_SMBUS directly? Selecting I2C_SMBUS is what device drivers are indeed supposed to do. However doing it from i2c-core seems awkward, because i2c-smbus itself depends on i2c-core. If they end up both built in, I guess it will be fine. But if they are modular, I'm afraid you won't be able to load the modules, because each of them requires the other to be loaded first for proper symbol resolution. -- Jean Delvare SUSE L3 Support -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
