From: Flameeyes <daps_mls@libero.it>
To: Greg KH <greg@kroah.com>
Cc: Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test2, sensors and sysfs
Date: 31 Jul 2003 19:01:24 +0200 [thread overview]
Message-ID: <1059670884.23098.18.camel@laurelin> (raw)
In-Reply-To: <20030731165056.GA3622@kroah.com>
On Thu, 2003-07-31 at 18:50, Greg KH wrote:
> What sensor drivers are you using in 2.4? Are these drivers even
> present in 2.6? Remember, a lot of them have not been ported yet.
The same, i2c-viapro and via686a, and they works well for mainboard, cpu
and system temperatures, and also for fans' rpms.
--
Flameeyes <dgp85@users.sf.net>
next prev parent reply other threads:[~2003-07-31 17:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 16:36 2.6.0-test2, sensors and sysfs Flameeyes
2003-07-31 16:50 ` Greg KH
2003-07-31 17:01 ` Flameeyes [this message]
2003-07-31 17:36 ` Greg KH
2003-07-31 16:52 ` Sergey Vlasov
[not found] ` <20030731211732.5591495d.vsu@altlinux.ru>
2003-07-31 18:02 ` Flameeyes
-- strict thread matches above, loose matches on Subject: below --
2003-07-31 17:21 Tomasz Torcz
2003-07-31 17:34 ` Greg KH
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=1059670884.23098.18.camel@laurelin \
--to=daps_mls@libero.it \
--cc=greg@kroah.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox