* Jean Delvare <khali at linux-fr.org> [2004-01-09 22:58:58 +0100]: > Shouldn't the asb100 be listed first, the same way the w83781d is, since > it has subclients? I would even put asb100 before w83781d, since for now > the w83781d driver will try to handle ASB100 chips too, thus preventing > the asb100 driver from being used if both drivers are built-in. You're right, thanks. Greg, please apply... * * * * * This patch fixes the link order for asb100 sensors chip driver. --- linux-2.6.1-rc1-mmh/drivers/i2c/chips/Makefile.orig 2003-12-31 18:07:45.000000000 -0500 +++ linux-2.6.1-rc1-mmh/drivers/i2c/chips/Makefile 2004-01-13 22:52:16.000000000 -0500 @@ -2,11 +2,11 @@ # Makefile for the kernel hardware sensors chip drivers. # -# w83781d goes first, as it can override other driver's addresses. +# asb100, then w83781d go first, as they can override other drivers' addresses. +obj-$(CONFIG_SENSORS_ASB100) += asb100.o obj-$(CONFIG_SENSORS_W83781D) += w83781d.o obj-$(CONFIG_SENSORS_ADM1021) += adm1021.o -obj-$(CONFIG_SENSORS_ASB100) += asb100.o obj-$(CONFIG_SENSORS_EEPROM) += eeprom.o obj-$(CONFIG_SENSORS_IT87) += it87.o obj-$(CONFIG_SENSORS_LM75) += lm75.o -- Mark M. Hoffman mhoffman at lightlink.com
