From: Randy Dunlap <randy.dunlap@xxxxxxxxxx> i2c-intel-mid driver uses PCI data structs and interfaces, so it should depend on PCI. Fixes these build errors: drivers/i2c/busses/i2c-intel-mid.c:977: error: implicit declaration of function 'pci_request_region' drivers/i2c/busses/i2c-intel-mid.c:1077: error: implicit declaration of function 'pci_release_region' Signed-off-by: Randy Dunlap <randy.dunlap@xxxxxxxxxx> Cc: Ba Zheng <zheng.ba@xxxxxxxxx> Cc: Jean Delvare <khali@xxxxxxxxxxxx> Cc: Ben Dooks <ben-linux@xxxxxxxxx> Cc: linux-i2c@xxxxxxxxxxxxxxx --- drivers/i2c/busses/Kconfig | 1 + 1 file changed, 1 insertion(+) --- linux-next-20101029.orig/drivers/i2c/busses/Kconfig +++ linux-next-20101029/drivers/i2c/busses/Kconfig @@ -398,6 +398,7 @@ config I2C_IMX config I2C_INTEL_MID tristate "Intel Moorestown/Medfield Platform I2C controller" + depends on PCI help Say Y here if you have an Intel Moorestown/Medfield platform I2C controller. -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
