From: Greg KH <greg@kroah.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: LM Sensors <lm-sensors@lm-sensors.org>,
LKML <linux-kernel@vger.kernel.org>,
Yani Ioannou <yani.ioannou@gmail.com>
Subject: Re: More hardware monitoring drivers ported to the new sysfs callbacks
Date: Sun, 5 Jun 2005 23:22:03 -0700 [thread overview]
Message-ID: <20050606062203.GA6344@kroah.com> (raw)
In-Reply-To: <20050605200901.41592fe9.khali@linux-fr.org>
On Sun, Jun 05, 2005 at 08:09:01PM +0200, Jean Delvare wrote:
> Hi all,
>
> I have been modifying three additional hardware monitoring drivers to
> take benefit of Yani Ioannou's new, extended sysfs callbacks. These
> drivers are lm63, lm83 and lm90. All of these are relatively small when
> compared to the first two modified drivers (adm1026 and it87). My goal
> was to demonstrate that the new callbacks can also be used in small
> drivers, with significant benefits. The result is even smaller drivers
> (less memory used when loaded), relying far less on macros, which makes
> the code easier to read (and the drivers presumably faster to distribute
> using distcc).
>
> Module Before After
> lm63 10128 9424 ( -704/ -6%)
> lm83 8784 6864 (-1920/-21%)
> lm90 12420 10628 (-1792/-14%)
>
> Individual patches will follow. Comments welcome. Greg, can you add
> these to one of your trees?
Applied, thanks.
> Before I go on with driver conversion, there are two points I'd like to
> discuss:
>
> First, I don't much like the name of the new header file,
> linux/i2c-sysfs.h. It isn't related with i2c at all! It's all about
> sensors (or hardware monitoring if you prefer). I think the header file
> should be named linux/hwmon-sysfs.h or something similar.
Sure, that would be fine.
> Second, is there a reason why the SENSOR_DEVICE_ATTR macro creates a
> stucture named sensor_dev_attr_##_name rather than simply
> dev_attr_##_name? As it seems unlikely that SENSOR_DEVICE_ATTR and
> DEVICE_ATTR will both be called for the same file, going for the short
> form shouldn't cause any problem. This would make the calling code more
> readable IMHO.
Hm, I really don't care either way about this.
thanks,
greg k-h
next prev parent reply other threads:[~2005-06-06 7:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-05 18:09 More hardware monitoring drivers ported to the new sysfs callbacks Jean Delvare
2005-06-05 18:25 ` Yani Ioannou
2005-06-05 18:32 ` [PATCH 2.6] I2C: (1/3) lm63 uses " Jean Delvare
2005-06-05 19:16 ` [PATCH 2.6] I2C: (2/3) lm83 " Jean Delvare
2005-06-05 19:27 ` [PATCH 2.6] I2C: (3/3) lm90 " Jean Delvare
2005-06-06 6:22 ` Greg KH [this message]
2005-06-06 17:34 ` More hardware monitoring drivers ported to the " Jean Delvare
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=20050606062203.GA6344@kroah.com \
--to=greg@kroah.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=yani.ioannou@gmail.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