From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Sensors-detect with DMI detection
Date: Fri, 23 Mar 2007 15:43:09 +0000 [thread overview]
Message-ID: <20070323164309.90169ec2.khali@linux-fr.org> (raw)
In-Reply-To: <00c901c7568f$60a3ad40$0801a8c0@pinkeltje>
Hi Hans,
On Fri, 23 Mar 2007 10:06:10 +0100, Hans de Goede wrote:
> Wouldn't it be wise to target only 3.x / 4.x with the dmi-detect code, and thus
> assume dynamic chip support and the new syntax? I haven't been doing much
> lm-sensors related work myself lately, but I can make some time free to get the
> dyn chip support into the 3.0 branch asap, if that helps the dmi detect code to
> become future proof. I think only support 3.x / 4.x is easiest / best otherwise
> the code becomes convoluted with compatibility muck from the day it was written.
I tend to agree, yeah. The only problem is that I cannot give any
timeline for the dyn chip support, as I do not have the time to work on
it myself. But if you're going to do it, alright.
--
Jean Delvare
prev parent reply other threads:[~2007-03-23 15:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 14:40 [lm-sensors] Sensors-detect with DMI detection Ivo Manca
2007-02-22 17:19 ` Jean Delvare
2007-02-23 7:08 ` Hans de Goede
2007-02-27 8:50 ` Jean Delvare
2007-02-27 10:59 ` Ivo Manca
2007-02-27 11:43 ` Jean Delvare
2007-02-27 12:24 ` Ivo Manca
2007-02-27 20:41 ` Rudolf Marek
2007-02-28 13:35 ` Hans de Goede
2007-02-28 13:44 ` Jasper Alias
2007-03-01 7:46 ` Jean Delvare
2007-03-01 8:13 ` Hans de Goede
2007-03-01 8:54 ` Jean Delvare
2007-03-16 13:06 ` Ivo Manca
2007-03-18 20:29 ` Jean Delvare
2007-03-20 12:39 ` Ivo Manca
2007-03-22 10:09 ` Ivo Manca
2007-03-23 8:59 ` Jean Delvare
2007-03-23 9:06 ` Hans de Goede
2007-03-23 15:43 ` 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=20070323164309.90169ec2.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.