From: mhoffman@lightlink.com (Mark M. Hoffman)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] [PATCH] lm93 driver for 2.6, second try
Date: Wed, 03 Aug 2005 02:08:56 +0000 [thread overview]
Message-ID: <20050803000840.GA24464@jupiter.solarsys.private> (raw)
In-Reply-To: <1122934191.32459.18.camel@wiz.dev.aspsys.com>
Hi Eric:
> On Tue, 2005-08-02 at 16:33, Mark M. Hoffman wrote:
> > CVS/lm93.c, line 450:
> >
> > result = i2c_smbus_read_block_data(client,
> >
> > Your patch, at the equivalent place:
> >
> > result = i2c_smbus_read_i2c_block_data(client,
> >
> > Those two aren't synonyms - you changed the transaction type. Why?
* Eric J. Bowersox <ericb@aspsys.com> [2005-08-02 17:08:45 -0600]:
> Well, for one thing, the function i2c_smbus_read_block_data doesn't seem
> to exist anymore, though its twin, i2c_smbus_write_block_data, does.
> (See: include/linux/i2c.h, lines 99-103, in 2.6.13-rc3-mm3.)
>
> You're right that there is a difference in the underlying
> implementations, but the old (and presumably correct, in this instance)
> function appears to have been removed sometime between 2.6.5 and
> 2.6.13-rc3-mm3. Anyone have any idea why that was done? As a
Yes, I remembered that just as your message was coming in. It was
removed because there were no in-kernel users, so it was considered
bloat.
> workaround, should I basically create my own implementation of the old
> i2c_smbus_read_block_data by calling i2c_smbus_xfer myself?
No, please create a separate patch that puts it back into i2c-core
where it belongs.
> > (You also reminded me that i2c-i801.c in 2.6.x should get synced up
> > a bit with its twin in lm-sensors CVS. I'll do that later.)
>
> Yeah, in particular, in the "prochot" reporting, I noticed that you
> seemed to be reporting the "average" return value twice. In
> kernel/chips/lm93.c, lines 1113-1115, it reads:
> [...]
I really meant the i2c-i801 driver, not the lm93. But, if you found
some bug in CVS/lm93.c then by all means send me a patch and I'll
commit it. I still haven't been able to review your port closely
yet, sorry.
Regards,
--
Mark M. Hoffman
mhoffman@lightlink.com
next prev parent reply other threads:[~2005-08-03 2:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 7:58 [lm-sensors] [PATCH] lm93 driver for 2.6, second try Eric J. Bowersox
2005-08-02 21:10 ` Eric J. Bowersox
2005-08-02 22:48 ` Eric J. Bowersox
2005-08-03 0:33 ` Rudolf Marek
2005-08-03 0:34 ` Mark M. Hoffman
2005-08-03 1:09 ` Eric J. Bowersox
2005-08-03 2:08 ` Mark M. Hoffman [this message]
2005-08-05 13:47 ` Rudolf Marek
2005-08-05 21:30 ` Eric J. Bowersox
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=20050803000840.GA24464@jupiter.solarsys.private \
--to=mhoffman@lightlink.com \
--cc=lm-sensors@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.