From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [PATCH 2.4] i2c cleanups
Date: Thu, 19 May 2005 06:24:31 +0000 [thread overview]
Message-ID: <20031228152909.50a37848.khali@linux-fr.org> (raw)
In-Reply-To: <20031213191258.2d78a9f7.khali@linux-fr.org>
> Forget about -km-2 and -km-6. I will post them in smaller parts.
Never received -km-6, so I can forget about it very easily ;) What about
-km-4?
As for -km-2, don't forget that there is no real use splitting patches
if parts cannot be applied independantly. And I repeat myself, please
first fix module reference counting in CVS before posting any patch
related to this point. Again, we cannot send anything to Marcelo with
regression in it.
> Patch -km-7 : Drop 2.2 code.
> Patch -km-8 : User progs don't include kernel files.
> Patch -km-9 : Message block size.
> Patch -km-10 : Remove SLO_IO in algo-bit.
> Patch -km-11 : Bus scan removal, bit & pcf.
> Patch -km-12 : Add new IDs.
> Patch -km-13 : Unused code, whitespace.
Great. I already have patches for 10 and 11 (more complete since it also
handles drivers that are not in our CVS repository). I will take a look
at your patches in a while, as time permits.
> Yes, christmas got cancelled ;)
;) You know, we merely depend on Marcelo for having our patches applied.
I don't plan to submit anything new until he approved (or disapproved)
the previous wave of patches. This of course doesn't prevent us from
working on new patches, but there's no need skipping Christmas if you
don't want to. Unless you, like I, don't enjoy these days too much and
were after some kind of excuse for missing them ;)
--
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/
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
2003-12-13 18:12 [PATCH 2.4] i2c cleanups Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2003-12-13 18:33 ` [PATCH 2.4] i2c cleanups (1/4) Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2003-12-13 18:49 ` [PATCH 2.4] i2c cleanups (2/4) Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2003-12-13 19:31 ` [PATCH 2.4] i2c cleanups (3/4) Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2003-12-13 19:36 ` [PATCH 2.4] i2c cleanups (4/4) Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` [PATCH 2.4] i2c cleanups Kyösti Mälkki
2005-05-19 6:24 ` Kyösti Mälkki
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Greg KH
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Kyösti Mälkki
2005-05-19 6:24 ` Kyösti Mälkki
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Kyösti Mälkki
2005-05-19 6:24 ` Kyösti Mälkki
2005-05-19 6:24 ` Kyösti Mälkki
2005-05-19 6:24 ` Jean Delvare [this message]
2005-05-19 6:24 ` Kyösti Mälkki
2005-05-19 6:24 ` Kyösti Mälkki
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Kyösti Mälkki
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=20031228152909.50a37848.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.