From: Jean Delvare <khali@linux-fr.org>
To: Linux I2C <i2c@lm-sensors.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Wanted: i2c subsystem co-maintainer
Date: Tue, 4 Mar 2008 18:45:12 +0100 [thread overview]
Message-ID: <20080304184512.3f78d296@hyperion.delvare> (raw)
Hi all,
I have a hard time maintaining the i2c subsystem alone. New drivers
and, more importantly, subsystem evolutions are submitted much faster
than I can review and merge them. I am hearing complaints about this.
It has been lasting for a while now and it doesn't seem like the
situation is going to improve. Thus, I think it would be better if
someone was co-maintaining the i2c subsystem with me.
So, if anyone is interested in co-maintaining the i2c subsystem with
me, please let me know. The ideal candidate would come from the
embedded world, as I have absolutely no experience with this myself and
most of the new drivers are for embedded devices, and should have
contributed to the kernel in a significant way already.
Thanks,
--
Jean Delvare
next reply other threads:[~2008-03-04 17:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 17:45 Jean Delvare [this message]
2008-03-25 8:50 ` [i2c] Wanted: i2c subsystem co-maintainer Jean Delvare
2008-05-15 10:16 ` Ben Dooks
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=20080304184512.3f78d296@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=i2c@lm-sensors.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox