linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Pierre Ossman <pierre@ossman.eu>
Cc: linux-kernel@vger.kernel.org, linux-embedded@vger.kernel.org,
	nico@cam.org, nicolas.ferre@rfo.atmel.com, hskinnemoen@atmel.com,
	tony@atomide.com, david-b@pacbell.net, manuel.lauss@gmail.com,
	mirq-linux@rere.qmqm.pl, ppisa@pikron.com,
	jarkko.lavinen@nokia.com, ben@fluff.org, saschasommer@freenet.de,
	avorontsov@ru.mvista.com, oakad@yahoo.com, ian@mnementh.co.uk,
	HaraldWelte@viatech.com, JosephChan@via.com.tw,
	adrian.hunter@nokia.com
Subject: Re: New MMC maintainer needed
Date: Wed, 22 Jul 2009 15:17:44 -0700	[thread overview]
Message-ID: <20090722151744.fffd7bf5.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090714153601.6dfe70ff@mjolnir.ossman.eu>

On Tue, 14 Jul 2009 15:36:01 +0200
Pierre Ossman <pierre@ossman.eu> wrote:

> I'm afraid the time has come for me to step down as maintainer for the
> MMC/SD/SDIO subsystem and for someone else to take over the rudder. It
> is no secret that I haven't been able to give the maintainer role the
> resources it required, and as a result it has gone from being a fun
> hobby to a burdensome chore. I was hoping it was a temporary slump, but
> this has been the norm for over a year now, so it's time for me to
> throw in the towel.
> 
> I don't have any clear nominees for a replacement, but if you feel that
> you are in a position to take over the maintainer role then please
> raise your hand.
> 
> I only have a few patches in my queue right now and I can push those
> off to Linus before I quit. There are however a lot of unhandled
> messages that need attention. I can provide a list once a successor has
> been named.
> 
> I realise that you have put a lot of time and effort into the patches
> you send me and I am truly sorry that I haven't been able to handle
> them better. Hopefully me stepping down means that we get someone who
> can actually take care of everything in a timely manner.
> 
> I haven't decided what to do with the sdhci maintainership yet. Right
> now I only know I need a break and freeing myself from the MMC
> maintainer role is the first step. Hopefully I can return as a
> developer in the future.
> 

Thanks, Pierre.

Until and unless someone else steps up I can act as maintainer of last
resort for MMC.  As I'm presently doing for fbdev, hwmon, rtc, spi,
gpio, i2o and about 1000 other identifiable subsystems.

Fortunately, MMC doesn't appear to have its own mailing list so I'll
actually get to see the patches.  I do monitor a couple of
subsystem-specific lists (fbdev, hwmon) but the delays can be awful - a
month or two.


When it comes to subsystems about which I have little knowledge I tend
to work as follows:

- scan the patch to see if anything stands out to my inexperienced eye

- if possible, comment on it to make a bit of noise and to let the
  submitter and others know that a) someone has looked at it and b)
  there's a chance that it'll be merged.

- try to identify some people who might have an interest in the patch
  and/or who might have related experience which would help them review
  this one effectively.

So if someone finds themselves cc'ed on an MMC email from myself,
please do take a bit of time to pass an eye across it, and let us know
that you have done so - it really helps.

  parent reply	other threads:[~2009-07-22 22:17 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-14 13:36 New MMC maintainer needed Pierre Ossman
2009-07-14 21:04 ` Ian Molton
2009-07-22 22:17 ` Andrew Morton [this message]
2009-07-23  0:08   ` Ian Molton
2009-07-23  5:54     ` Matt Fleming
2009-07-23  6:22       ` Andrew Morton
2009-07-23  6:42         ` Paul Mundt
2009-07-23  6:50         ` Ohad Ben-Cohen
2009-07-23 13:52           ` Matt Fleming
2009-07-24 22:29             ` Andrew Morton
2009-07-27  6:06               ` Philip Langdale
2009-07-27 12:09                 ` David Vrabel
2009-07-27 21:40                   ` Matt Fleming
2009-07-28  0:52                     ` Philip Langdale
2009-07-28 12:51                     ` David Vrabel
2009-07-23  7:01         ` Adrian Hunter
2009-07-23  7:25         ` Stephen Rothwell
2009-07-23  7:32           ` Andrew Morton
2009-07-23  7:38             ` Stephen Rothwell
2009-07-23 16:29               ` Andi Kleen
2009-07-23 10:57       ` Roberto A. Foglietta
2009-07-28 20:22     ` Pierre Ossman
2009-07-30  2:36       ` Segher Boessenkool
2009-07-28 20:20   ` Pierre Ossman
2009-07-28 21:14     ` Ian Molton
2009-07-28 22:41       ` Andrew Morton
2009-07-29  6:35         ` Sam Ravnborg
2009-07-29 10:35         ` Ian Molton
2009-07-28 20:23   ` Pierre Ossman
2009-07-31 10:26     ` Pierre Ossman
2009-07-31 10:54       ` Matt Fleming
2009-08-03 10:34         ` Pierre Ossman
2009-08-03 11:10           ` Matt Fleming
2009-08-03 11:13           ` Adrian Hunter
2009-08-03 21:41             ` Andrew Morton
2009-08-11 14:02             ` Matt Fleming
2009-08-12 22:27               ` Andrew Morton
2009-08-13  8:21                 ` Matt Fleming
2009-08-13  7:01               ` Adrian Hunter
2009-08-13 17:03                 ` Nicolas Pitre
2009-08-04  1:51       ` David Brownell
2009-08-05  1:42         ` David VomLehn
2009-08-06  8:54         ` Pierre Ossman
2009-08-18  9:33       ` Nicolas Ferre
  -- strict thread matches above, loose matches on Subject: below --
2009-07-15  4:59 Alex Dubov
2009-07-31 13:36 ` Maxim Levitsky
2009-08-01  6:53   ` Alex Dubov
2009-08-01  7:21     ` Maxim Levitsky
2009-08-12 22:52 ellis

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=20090722151744.fffd7bf5.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=HaraldWelte@viatech.com \
    --cc=JosephChan@via.com.tw \
    --cc=adrian.hunter@nokia.com \
    --cc=avorontsov@ru.mvista.com \
    --cc=ben@fluff.org \
    --cc=david-b@pacbell.net \
    --cc=hskinnemoen@atmel.com \
    --cc=ian@mnementh.co.uk \
    --cc=jarkko.lavinen@nokia.com \
    --cc=linux-embedded@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manuel.lauss@gmail.com \
    --cc=mirq-linux@rere.qmqm.pl \
    --cc=nico@cam.org \
    --cc=nicolas.ferre@rfo.atmel.com \
    --cc=oakad@yahoo.com \
    --cc=pierre@ossman.eu \
    --cc=ppisa@pikron.com \
    --cc=saschasommer@freenet.de \
    --cc=tony@atomide.com \
    /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;
as well as URLs for NNTP newsgroup(s).