Re: mmotm 2009-11-24-16-47 uploaded (gpio_max7301)

[Randy Dunlap <rdunlap@xenotime.net>]

akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2009-11-24-16-47 has been uploaded to
> 
>    http://userweb.kernel.org/~akpm/mmotm/
> 
> and will soon be available at
> 
>    git://git.zen-sources.org/zen/mmotm.git
> 
> It contains the following patches against 2.6.32-rc8:
>
> gpio-add-driver-for-max7300-i2c-gpio-extender.patch

This driver has build failures when CONFIG_I2C=m and
MAX7301=y, MAX7301_I2C=y, MAX7301_SPI=y:

drivers/built-in.o: In function `max7301_i2c_write':
max7301.c:(.text+0x2d9e): undefined reference to `i2c_smbus_write_byte_data'
drivers/built-in.o: In function `max7301_i2c_read':
max7301.c:(.text+0x2dc6): undefined reference to `i2c_smbus_read_byte_data'
drivers/built-in.o: In function `max7301_init':
max7301.c:(.init.text+0x42e): undefined reference to `i2c_register_driver'
max7301.c:(.init.text+0x496): undefined reference to `i2c_del_driver'
drivers/built-in.o: In function `max7301_exit':
max7301.c:(.exit.text+0x14): undefined reference to `i2c_del_driver'


This kconfig syntax:

config GPIO_MAX7301
        tristate "Maxim MAX730x GPIO expander"
        depends on I2C || SPI_MASTER

allows GPIO_MAX7301 to be y when SPI_MASTER=y and I2C=m.
If you want to do that, you'll need to handle CONFIG_I2C=m somehow.


-- 
~Randy