From: Martin Dalecki <dalecki@evision-ventures.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Matthias Andree <matthias.andree@stud.uni-dortmund.de>,
linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.18-pre9-mjc2
Date: Thu, 14 Feb 2002 13:34:04 +0100 [thread overview]
Message-ID: <3C6BAEBC.3090002@evision-ventures.com> (raw)
In-Reply-To: <E16bL89-0008Jl-00@the-village.bc.nu>
Alan Cox wrote:
>>>lm_sensors (lm_sensors team)
>>>
>>Hum, the last time I merged that stuff into my own kernel, the
>>patch-generator that they ship did not include all of the drivers I
>>needed. Also, I'm missing i2c from your patch list. Is that intentional
>>or is the i2c patch not needed? Which lm_sensors version did you merge?
>>
>
>Be very careful merging lm_sensors. Incorrect use of it is a wonderful
>way to do things like totally destroy (back to factory) an ibm thinkpad.
>
Well that is only one single sensor driver... The rest work's rather nicely.
next prev parent reply other threads:[~2002-02-14 12:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-14 4:58 Linux 2.4.18-pre9-mjc2 Michael Cohen
2002-02-14 5:09 ` Michael Cohen
2002-02-14 10:26 ` Lionel Bouton
2002-02-14 5:12 ` Andrew Hatfield
2002-02-14 5:19 ` Larry McVoy
2002-02-14 13:58 ` Ed Tomlinson
2002-02-14 5:46 ` Andrew Hatfield
2002-02-14 5:48 ` Michael Cohen
2002-02-14 5:51 ` William Lee Irwin III
2002-02-14 11:43 ` Matthias Andree
2002-02-14 12:36 ` Alan Cox
2002-02-14 12:34 ` Martin Dalecki [this message]
2002-02-17 13:45 ` Pavel Machek
2002-02-18 19:04 ` Alan Cox
2002-02-18 20:58 ` Pavel Machek
2002-02-18 21:16 ` Alan Cox
2002-02-18 21:08 ` Pavel Machek
2002-02-18 21:39 ` Alan Cox
2002-02-18 21:43 ` Kjartan Maraas
2002-02-19 9:22 ` Pavel Machek
2002-02-19 9:47 ` Alan Cox
2002-02-20 11:33 ` Pavel Machek
2002-02-15 3:18 ` Linux 2.4.18-pre9-mjc2 & Rmap12f [PATCH] Mike Fedyk
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=3C6BAEBC.3090002@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.andree@stud.uni-dortmund.de \
/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