From: Mike Fedyk <mfedyk@matchmail.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: Greg KH <greg@kroah.com>, "J.A. Magallon" <jamagallon@able.es>,
"Prakash K. Cheemplavam" <PrakashKC@gmx.de>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
sensors@Stimpy.netroedge.com
Subject: Re: 2.6.3-mm4
Date: Fri, 27 Feb 2004 10:16:42 -0800 [thread overview]
Message-ID: <403F898A.2000801@matchmail.com> (raw)
In-Reply-To: <1077870909.403f013dd04b6@imp.gcu.info>
Jean Delvare wrote:
> Quoting Greg KH <greg@kroah.com>:
>
>
>>Anyway, I think all you need to do is get the cvs tree of the
>>lmsensors package. Sensors people, the needed changes are commited
>>into the tree, right?
>
>
> No. The changes are waiting in my local repository, ready to be applied.
> I didn't want to apply them because we were supposed to release
> lm_sensors 2.8.5 (for Linux 2.6.3 users) and the sysfs names change
> wouldn't belong there.
>
> The libsensors patches are available on my personal server here:
> http://jdelvare.net1.nerim.net/sensors/
> Apply both patches in order and you'll get a 2.6.3-mm4-compliant
> library.
>
> I will apply the libsensors changes to the CVS repository as soon as the
> kernel modules changes are accepted into Linus' tree. If we did not
> release a new version since there, I'll take a CVS snapshot right
> before so that Linux 2.6.3 users have a usable version available (but
> my preference strongly goes to releasing 2.8.5 instead).
You have to be kidding me. Are you saying that with your patches to
libsensors it won't support 2.6.3 style sensor sysfs names?
next prev parent reply other threads:[~2004-02-27 18:18 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-26 2:55 2.6.3-mm4 Andrew Morton
2004-02-26 8:22 ` 2.6.3-mm4 Alexander Hoogerhuis
2004-02-26 8:48 ` 2.6.3-mm4 Marc-Christian Petersen
2004-02-26 8:51 ` 2.6.3-mm4 Nuno Silva
2004-02-27 0:48 ` 2.6.3-mm4 Greg KH
2004-02-26 15:50 ` 2.6.3-mm4 David Martínez Moreno
2004-02-26 15:59 ` 2.6.3-mm4 Christoph Hellwig
2004-02-26 16:30 ` 2.6.3-mm4 (compile stats) John Cherry
2004-02-26 18:59 ` Mike Fedyk
2004-02-26 19:26 ` John Cherry
2004-02-26 18:50 ` 2.6.3-mm4 Matthias Hentges
2004-02-26 23:35 ` 2.6.3-mm4, sensors broken Prakash K. Cheemplavam
2004-02-27 0:03 ` Andrew Morton
2004-02-27 8:58 ` Prakash K. Cheemplavam
2004-02-27 0:11 ` 2.6.3-mm4 J.A. Magallon
2004-02-27 0:46 ` 2.6.3-mm4 Greg KH
2004-02-27 8:35 ` 2.6.3-mm4 Jean Delvare
2004-02-27 18:16 ` Mike Fedyk [this message]
2004-02-27 19:59 ` 2.6.3-mm4 Jean Delvare
2004-02-29 7:51 ` 2.6.3-mm4 Mike Fedyk
2004-02-29 10:11 ` 2.6.3-mm4 Jean Delvare
2004-02-27 16:48 ` 2.6.3-mm4 Prakash K. Cheemplavam
2004-02-27 9:00 ` 2.6.3-mm4 Prakash K. Cheemplavam
2004-02-27 23:51 ` 2.6.3-mm4 Adrian Bunk
2004-03-01 8:25 ` MM VM patches was: 2.6.3-mm4 Mike Fedyk
2004-03-01 8:44 ` Nick Piggin
2004-03-01 9:05 ` Mike Fedyk
2004-03-01 9:27 ` Nick Piggin
2004-03-01 9:47 ` Mike Fedyk
2004-03-01 9:10 ` Nick Piggin
2004-03-01 9:52 ` [PATCH] 2.6.4-rc1-mm1: vm-kswapd-incremental-min (was Re: MM VM patches was: 2.6.3-mm4) Nick Piggin
2004-03-01 10:18 ` Andrew Morton
2004-03-01 10:29 ` Nick Piggin
[not found] <A6974D8E5F98D511BB910002A50A6647615F33F5@hdsmsx402.hd.intel.com>
2004-02-26 22:40 ` 2.6.3-mm4 Len Brown
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=403F898A.2000801@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=PrakashKC@gmx.de \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=jamagallon@able.es \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sensors@Stimpy.netroedge.com \
/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