public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Dubov <oakad@yahoo.com>
To: LKML <linux-kernel@vger.kernel.org>,
	linux-embedded@vger.kernel.org, Nicolas Pitre <nico@cam.org>,
	Nicolas Ferre <nicolas.ferre@rfo.atmel.com>,
	Haavard Skinnemoen <hskinnemoen@atmel.com>,
	Tony Lindgren <tony@atomide.com>,
	David Brownell <david-b@pacbell.net>,
	manuel.lauss@gmail.com, mirq-linux@rere.qmqm.pl,
	Pavel Pisa <ppisa@pikron.com>,
	Jarkko Lavinen <jarkko.lavinen@nokia.com>,
	Ben Dooks <ben@fluff.org>,
	saschasommer@freenet.de, avorontsov@ru.mvista.com,
	ian@mnementh.co.uk, HaraldWelte@viatech.com,
	JosephChan@via.com.tw, Adrian Hunter <adrian.hunter@nokia.com>,
	Pierre Ossman <pierre@ossman.eu>
Subject: Re: New MMC maintainer needed
Date: Tue, 14 Jul 2009 21:59:04 -0700 (PDT)	[thread overview]
Message-ID: <812689.20578.qm@web37604.mail.mud.yahoo.com> (raw)


> 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.

What an unfortunate thing.

Franky speaking, I couldn't manage any time to work on Linux
in the last year myself. I had such a great plans for Memstick
and such, yet none advanced.

At this rate, the future of the flash cards on Linux will
become highly uncertain.
:-(



      

             reply	other threads:[~2009-07-15  5:05 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-15  4:59 Alex Dubov [this message]
2009-07-31 13:36 ` New MMC maintainer needed Maxim Levitsky
2009-08-01  6:53   ` Alex Dubov
2009-08-01  7:21     ` Maxim Levitsky
  -- strict thread matches above, loose matches on Subject: below --
2009-07-14 13:36 Pierre Ossman
2009-07-14 21:04 ` Ian Molton
2009-07-22 22:17 ` Andrew Morton
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

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=812689.20578.qm@web37604.mail.mud.yahoo.com \
    --to=oakad@yahoo.com \
    --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=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