On Wed, May 27, 2009 at 09:18:31AM +0200, Jean Delvare wrote: > On Wed, 27 May 2009 16:08:50 +0900, Paul Mundt wrote: > > Another day, another module-related failure due to the i2c interface > > being used in code that optionally uses it: > > > > ERROR: "i2c_new_device" [drivers/media/video/soc_camera.ko] undefined! > > ERROR: "i2c_get_adapter" [drivers/media/video/soc_camera.ko] undefined! > > ERROR: "i2c_put_adapter" [drivers/media/video/soc_camera.ko] undefined! > > ERROR: "i2c_unregister_device" [drivers/media/video/soc_camera.ko] undefined! > > make[2]: *** [__modpost] Error 1 > > make[1]: *** [modules] Error 2 > > make: *** [sub-make] Error 2 > > > > In the interest of not continually inserting i2c ifdefs in to every > > driver that supports an optional i2c interface, this provides a stubbed > > set of interfaces for the CONFIG_I2C=n case. > > > > I've covered the obvious ones that cause the majority of the build > > failures, anything more involved really ought to have its dependencies > > fixed instead. > > Violent nack. Drivers which optionally use I2C are a minority. If they were a minority we wouldn't be hitting them on a weekly basis, and other busses already do similar things for similar reasons. You may not like it, but it's much less distasteful than littering random i2c ifdefs around every driver that chooses to have an optional i2c interface. If every multi-bus driver was forced to go through these sorts of hoops, the drivers would be even less readable than they already are today. -- 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
