From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: LAK <linux-arm-kernel@lists.arm.linux.org.uk>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: MMC maintainership help needed
Date: Mon, 03 Nov 2008 14:38:40 +0100 [thread overview]
Message-ID: <490EFEE0.8030104@atmel.com> (raw)
In-Reply-To: <20081029184254.56e05c4f@mjolnir.drzeus.cx>
Hi Pierre,
Pierre Ossman :
> I'm having trouble finding time and energy for handling MMC stuff in a
> timely manner (as those of you sending patches to me have noticed).
> Therefore I'm sending out this general plea for assistance.
>
> If you see any MMC/SD/SDIO patches, bug reports or general questions,
> don't be afraid to comment and/or ask for more information. Even if you
> don't feel like you can solve the issue, any help you can provide means
> that my limited time can be better spent. And you'll probably also get
> more comfortable with the MMC parts in the process. :)
Ok.
> On a related note, I see very little comments to my reviews except from
> the original author. As such I'm having a hard time evaluating my role.
> Are people satisified with my work as a gatekeeper or am I just being a
> pain in the ass? I know I can be a bit anal at times. :)
Hey Pierre, you are just perfect in this role from my point of view.
With many contributors, we manage to enhance significantly the quality
of the at91_mci SD/MMC driver and your view and comments, as a
maintainer, have always been valuable.
Kind regards,
--
Nicolas Ferre
next prev parent reply other threads:[~2008-11-03 13:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 17:42 MMC maintainership help needed Pierre Ossman
2008-10-29 18:13 ` Ian Molton
2008-10-30 9:03 ` Pierre Ossman
2008-10-30 13:35 ` Matt Fleming
2008-10-30 21:20 ` Dmitry Baryshkov
2008-11-03 4:07 ` Bill Gatliff
2008-11-03 13:38 ` Nicolas Ferre [this message]
2008-11-04 7:30 ` Madhusudhan Chikkature
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=490EFEE0.8030104@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=drzeus-list@drzeus.cx \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--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