From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: linux-2.4/MAINTAINERS, i2c drivers
Date: Thu, 19 May 2005 06:24:19 +0000 [thread overview]
Message-ID: <1064476786.3f72a0728dbdb@imp.gcu.info> (raw)
Dear Simon and Frodo,
I am planning to submit a patch to the MAINTAINERS files in Linux 2.4.
It seems that the "I2C DRIVERS" record is out of date. Frodo regularly
forwards mails to our mailing list. I haven't heard from Simon for
months. You both made remarkable work on Linux I2C layer, but maybe it's
time to update the record to point to active developers, lists and web
sites. It would ease communications between all actors, wouldn't it?
I volunteer to be the new maintainer of the i2c subsystem in 2.4. Greg
is already doing a great job in 2.6.
To the questions now:
Is a record update OK?
Are the following mailing list and web site still alive?
L: linux-i2c@pelican.tk.uni-linz.ac.at
W: http://www.tk.uni-linz.ac.at/~simon/private/i2c
Should they be kept in the record?
Here is my proposal of new record. Please tell me what you do think
about it:
I2C DRIVERS
P: Jean Delvare
M: khali@linux-fr.org
L: sensors@stimpy.netroedge.com
W: http://www.lm-sensors.nu/
S: Maintained
Would it make sense to split the record into "I2C SUBSYSTEM" and "SENSOR
DRIVERS"? "I2C DRIVERS" doesn't really make sense, there are much more
I2C drivers in the kernel than just ours. On the other hand, we have
non-sensor drivers in our repository.
Comments welcome.
--
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/
-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/
next reply other threads:[~2005-05-19 6:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:24 Jean Delvare [this message]
2005-05-19 6:24 ` Fw: linux-2.4/MAINTAINERS, i2c drivers DI Dr Simon Vogl
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=1064476786.3f72a0728dbdb@imp.gcu.info \
--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.