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.3-rc1
Date: Mon, 9 Feb 2004 15:19:35 -0800 [thread overview]
Message-ID: <10763687754014@kroah.com> (raw)
In-Reply-To: <10763687741075@kroah.com>
ChangeSet 1.1500.11.3, 2004/02/02 14:51:45-08:00, khali@linux-fr.org
[PATCH] I2C: Bring w83l785ts in compliance with sysfs naming conventions
Here is a patch that brings the w83l785ts driver in compliance with
sysfs naming conventions. This is pretty much the same problem and
solution that occured very recently with the lm75 and lm78 drivers.
The patch was tested to work fine by James Bolt.
drivers/i2c/chips/w83l785ts.c | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff -Nru a/drivers/i2c/chips/w83l785ts.c b/drivers/i2c/chips/w83l785ts.c
--- a/drivers/i2c/chips/w83l785ts.c Mon Feb 9 15:05:59 2004
+++ b/drivers/i2c/chips/w83l785ts.c Mon Feb 9 15:05:59 2004
@@ -137,8 +137,8 @@
return sprintf(buf, "%d\n", TEMP_FROM_REG(data->temp_over));
}
-static DEVICE_ATTR(temp_input, S_IRUGO, show_temp, NULL)
-static DEVICE_ATTR(temp_max, S_IRUGO, show_temp_over, NULL)
+static DEVICE_ATTR(temp_input1, S_IRUGO, show_temp, NULL)
+static DEVICE_ATTR(temp_max1, S_IRUGO, show_temp_over, NULL)
/*
* Real code
@@ -249,8 +249,8 @@
*/
/* Register sysfs hooks */
- device_create_file(&new_client->dev, &dev_attr_temp_input);
- device_create_file(&new_client->dev, &dev_attr_temp_max);
+ device_create_file(&new_client->dev, &dev_attr_temp_input1);
+ device_create_file(&new_client->dev, &dev_attr_temp_max1);
return 0;
next prev parent reply other threads:[~2004-02-09 23:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-09 23:13 [BK PATCH] i2c driver fixes for 2.6.3-rc1 Greg KH
2004-02-09 23:19 ` [PATCH] " Greg KH
2004-02-09 23:19 ` Greg KH
2004-02-09 23:19 ` Greg KH [this message]
2004-02-09 23:19 ` Greg KH
2004-02-09 23:19 ` Greg KH
2004-02-09 23:19 ` Greg KH
2004-02-09 23:19 ` Greg KH
2004-02-09 23:19 ` 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=10763687754014@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