From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Patch: Kernel 2.6 and multiple buses
Date: Sat, 10 Sep 2005 22:46:12 +0000 [thread overview]
Message-ID: <20050910224535.2eade133.khali@linux-fr.org> (raw)
In-Reply-To: <43215B5F.7050100@megware.com>
Hi again Karsten,
Quoting myself:
> Thanks a lot for this patch. I had been investigating this bug some
> times ago but could never figure out what the problem was. It's really
> great that you did succeed in finding the reason. I know it'll make a
> few other users happy too.
OK, I committed your patch, and also removed the algorithm name
comparison from the bus match test. Additionally, I dropped some
algorithm stuff from i2cbusses.c (which affects i2cset, i2cdump and
i2cdetect), sensors-detect and sensord, so that people stop wondering
about "unavailable algorithm name" messages.
I would appreciate if you could give a try to lm_sensors CVS and confirm
that it still works OK for you.
Thanks again for your contribution,
--
Jean Delvare
prev parent reply other threads:[~2005-09-10 22:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 11:53 [lm-sensors] Patch: Kernel 2.6 and multiple buses Karsten Petersen
2005-09-09 16:54 ` Jean Delvare
2005-09-10 22:46 ` Jean Delvare [this message]
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=20050910224535.2eade133.khali@linux-fr.org \
--to=khali@linux-fr.org \
--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.