From: mfedyk@matchmail.com (Mike Fedyk)
To: LKML <linux-kernel@vger.kernel.org>,
LM Sensors <sensors@Stimpy.netroedge.com>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Subject: [PATCH 2.4] i2c cleanups, third wave
Date: Thu, 19 May 2005 06:24:34 +0000 [thread overview]
Message-ID: <20040112014840.GE17845@matchmail.com> (raw)
In-Reply-To: <20040111144214.7a6a4e59.khali@linux-fr.org>
On Sun, Jan 11, 2004 at 02:42:14PM +0100, Jean Delvare wrote:
> I will be sending 8 patches to you, based on linux-2.4.25-pre4. They
> contain cleanups for the i2c subsystem code, ported from LM Sensors' i2c
> CVS repository [1]. Since that repository was also the base of the i2c
> subsystem as is now in linux 2.6, one might also consider these patches
> as backports from linux 2.6.
How about some patches to add some more sensors to the 2.4 kernel, like the
ones already in 2.6?
WARNING: multiple messages have this Message-ID (diff)
From: Mike Fedyk <mfedyk@matchmail.com>
To: LKML <linux-kernel@vger.kernel.org>,
LM Sensors <sensors@Stimpy.netroedge.com>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Subject: Re: [PATCH 2.4] i2c cleanups, third wave
Date: Sun, 11 Jan 2004 17:48:40 -0800 [thread overview]
Message-ID: <20040112014840.GE17845@matchmail.com> (raw)
In-Reply-To: <20040111144214.7a6a4e59.khali@linux-fr.org>
On Sun, Jan 11, 2004 at 02:42:14PM +0100, Jean Delvare wrote:
> I will be sending 8 patches to you, based on linux-2.4.25-pre4. They
> contain cleanups for the i2c subsystem code, ported from LM Sensors' i2c
> CVS repository [1]. Since that repository was also the base of the i2c
> subsystem as is now in linux 2.6, one might also consider these patches
> as backports from linux 2.6.
How about some patches to add some more sensors to the 2.4 kernel, like the
ones already in 2.6?
next prev parent reply other threads:[~2005-05-19 6:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-11 13:42 [PATCH 2.4] i2c cleanups, third wave Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2004-01-11 13:51 ` [PATCH 2.4] i2c cleanups, third wave (1/8) Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2004-01-11 13:59 ` [PATCH 2.4] i2c cleanups, third wave (2/8) Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2004-01-11 14:08 ` [PATCH 2.4] i2c cleanups, third wave (3/8) Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2004-01-11 14:50 ` [PATCH 2.4] i2c cleanups, third wave (4/8) Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Marcelo Tosatti
2004-01-11 15:04 ` [PATCH 2.4] i2c cleanups, third wave (5/8) Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2004-01-11 15:10 ` [PATCH 2.4] i2c cleanups, third wave (6/8) Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2004-01-11 15:20 ` [PATCH 2.4] i2c cleanups, third wave (7/8) Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2004-01-11 15:28 ` [PATCH 2.4] i2c cleanups, third wave (8/8) Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2004-01-12 1:48 ` Mike Fedyk [this message]
2005-05-19 6:24 ` [PATCH 2.4] i2c cleanups, third wave Mike Fedyk
2004-01-14 18:30 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2004-01-14 12:55 ` Marcelo Tosatti
2005-05-19 6:24 ` Marcelo Tosatti
2004-01-14 14:55 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark M. Hoffman
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=20040112014840.GE17845@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--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 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.