From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org, sensors@stimpy.netroedge.com
Subject: Re: [PATCH] i2c driver fixes for 2.6.1
Date: Mon, 19 Jan 2004 15:59:18 -0800 [thread overview]
Message-ID: <10745567584195@kroah.com> (raw)
In-Reply-To: <10745567584080@kroah.com>
ChangeSet 1.1474.98.4, 2004/01/14 11:11:06-08:00, mhoffman@lightlink.com
[PATCH] I2C: link asb100 in the proper order
* Jean Delvare <khali@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
* * * * *
This patch fixes the link order for asb100 sensors chip driver.
drivers/i2c/chips/Makefile | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff -Nru a/drivers/i2c/chips/Makefile b/drivers/i2c/chips/Makefile
--- a/drivers/i2c/chips/Makefile Mon Jan 19 15:32:50 2004
+++ b/drivers/i2c/chips/Makefile Mon Jan 19 15:32:50 2004
@@ -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
next prev parent reply other threads:[~2004-01-20 0:17 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 23:57 [BK PATCH] i2c driver fixes for 2.6.1 Greg KH
2004-01-19 23:59 ` [PATCH] " Greg KH
2004-01-19 23:59 ` Greg KH
2004-01-19 23:59 ` Greg KH
2004-01-19 23:59 ` Greg KH [this message]
2004-01-19 23:59 ` Greg KH
2004-01-19 23:59 ` Greg KH
2004-01-19 23:59 ` Greg KH
2004-01-19 23:59 ` Greg KH
2004-01-19 23:59 ` Greg KH
2004-01-19 23:59 ` Greg KH
2004-01-19 23:59 ` Greg KH
2004-01-19 23:59 ` Greg KH
2004-01-19 23:59 ` Greg KH
2004-01-19 23:59 ` Greg KH
2004-01-19 23:59 ` Greg KH
2004-01-19 23:59 ` Greg KH
2004-01-19 23:59 ` Greg KH
2004-01-19 23:59 ` Greg KH
2004-01-19 23:59 ` Greg KH
2004-01-19 23:59 ` Greg KH
2004-01-19 23:59 ` Greg KH
2004-01-19 23:59 ` Greg KH
2004-01-19 23:59 ` Greg KH
2004-01-19 23:59 ` Greg KH
2004-01-19 23:59 ` Greg KH
2004-01-19 23:59 ` Greg KH
2004-01-19 23:59 ` Greg KH
2004-01-19 23:59 ` Greg KH
2004-01-19 23:59 ` Greg KH
2004-01-21 21:50 ` Jean Delvare
2004-01-21 23:56 ` Greg KH
2004-01-31 8:56 ` Jean Delvare
2004-01-31 15:23 ` Greg KH
2004-01-20 22:03 ` Jean Delvare
2004-01-20 22:07 ` Greg KH
2004-01-21 20:47 ` Jean Delvare
2004-01-24 1:14 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=10745567584195@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sensors@stimpy.netroedge.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox