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:30 +0000 [thread overview]
Message-ID: <20031217202854.3914cb8d.khali@linux-fr.org> (raw)
In-Reply-To: <20031213191258.2d78a9f7.khali@linux-fr.org>
The 4 patches were accepted, you can see them in 2.4.23-bk13. A first
battle we won :) but the war is far from being over.
From 246kB for the patch that was required to update Linux 2.4.23 to
i2c 2.8.2, the patch size is reduced to 215kB with 2.4.23-bk13. If we
leave apart the new drivers, which I don't plan to submit, the remaining
size is 129k. This basically means that I've only done one fifth of the
job so far. I will sumbit another wave of patches as soon as possible.
There's something I would need help with. The main reason why we are
submitting patches is the change in the way module references are
counted. Sooner or later I'll have to submit a patch for that point. I
read on this list that the new method might not be correct though. I
don't want to submit a buggy patch this late in Linux 2.4's life, but on
the other hand I don't have the knowledge nor time to solve the problem,
if there is one. So I would like someone to review that part of our
code, to tell me if this is correct or not and why, and to commit the
required changes to our i2c CVS repository, if needed.
Ky?sti, you seem to understand the problem rather well, so I was
hoping you could help me here. MDS and Greg also would probably be able
to help. Guys, please work it out if you can. And remember that time is
against us, since a structure change won't be accepted after 2.4.24 is
released (it's not even sure it will be accepted *before*...)
If anyone else wants to help, this is very welcome too, of course ;)
--
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 ` Jean Delvare [this message]
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 ` 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 ` 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
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=20031217202854.3914cb8d.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.