From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Call for 2.9.2
Date: Tue, 06 Sep 2005 21:16:46 +0000 [thread overview]
Message-ID: <20050906211640.368eff4f.khali@linux-fr.org> (raw)
In-Reply-To: <20050716170208.7c1f7e3d.khali@linux-fr.org>
Hi Mark,
> Sure, I didn't think you wanted to perform major surgery just prior to
> the release.
And you were of course right at that. I was merely trying to figure out
what the next (post-release) steps would be if we went that direction.
And it looks OK to me.
> > 2* Eeproms are not the only affected chips. "sensors" displays empty
> > entries for all i2c chips that have a driver. This includes the
> > adv7176 and saa7110 video devices for me. They too will disappear
> > when one loads any hwmon driver. It should cause less surprise than
> > for eeprom, because no useful information is displayed, but it might
> > still confuse the users. I have no immediate solution though.
>
> Ooh, I didn't realize that: yeah, it's awkward. I suppose my
> suggested patch could be expanded into a blacklist - diminishing
> returns though.
On second thought, I'm not sure it's even worth the effort, as sensors
doesn't print anything for these chips in the first place, so I doubt
people will complain or even wonder. Also, the list of non-sensors i2c
chips is so long that a blacklist would be impossible to maintain
anyway.
> > Feel free to commit your patch BTW, it looks good.
>
> OK
Nice. I updated the FAQ to explain why the EEPROMs were disappearing
(4.33.2). I guess we are ready for release this time.
Philip, the next steps are up to you: bump the library version to 3.0.9,
and release!
Thanks,
--
Jean Delvare
next prev parent reply other threads:[~2005-09-06 21:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-16 17:02 [lm-sensors] Call for 2.9.2 Jean Delvare
2005-07-18 21:12 ` Jean Delvare
2005-08-14 14:42 ` Jean Delvare
2005-08-30 22:32 ` Jean Delvare
2005-08-31 1:42 ` Philip Edelbrock
2005-08-31 5:39 ` Mark M. Hoffman
2005-08-31 11:27 ` Jean Delvare
2005-08-31 11:37 ` Jean Delvare
2005-09-01 0:17 ` Philip Edelbrock
2005-09-01 10:40 ` Jean Delvare
2005-09-01 19:11 ` Philip Edelbrock
2005-09-05 18:33 ` Jean Delvare
2005-09-05 19:51 ` Mark M. Hoffman
2005-09-05 22:51 ` Jean Delvare
2005-09-06 5:28 ` Mark M. Hoffman
2005-09-06 21:16 ` Jean Delvare [this message]
2005-09-06 21:26 ` Philip Edelbrock
2005-09-06 22:16 ` Philip Edelbrock
2005-09-06 23:33 ` Henrik Brix Andersen
2005-09-07 16:02 ` Jean Delvare
2005-09-07 16:10 ` Henrik Brix Andersen
2005-09-07 16:20 ` 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=20050906211640.368eff4f.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.