[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090723003228.fc0ec34b.akpm@linux-foundation.org>
Date: Thu, 23 Jul 2009 00:32:28 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Matt Fleming <matt@...sole-pimps.org>,
Ian Molton <ian@...menth.co.uk>,
Pierre Ossman <pierre@...man.eu>, linux-kernel@...r.kernel.org,
linux-embedded@...r.kernel.org, nico@....org,
nicolas.ferre@....atmel.com, hskinnemoen@...el.com,
tony@...mide.com, david-b@...bell.net, manuel.lauss@...il.com,
mirq-linux@...e.qmqm.pl, ppisa@...ron.com,
jarkko.lavinen@...ia.com, ben@...ff.org, saschasommer@...enet.de,
avorontsov@...mvista.com, oakad@...oo.com, HaraldWelte@...tech.com,
JosephChan@....com.tw, adrian.hunter@...ia.com
Subject: Re: New MMC maintainer needed
On Thu, 23 Jul 2009 17:25:59 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi Andrew,
>
> On Wed, 22 Jul 2009 23:22:59 -0700 Andrew Morton <akpm@...ux-foundation.org> wrote:
> >
> > I actually already have a little pile of MMC things queued:
> >
> > http://userweb.kernel.org/~akpm/mmotm/broken-out/mmc-in-mmc_power_up-use-previously-selected-ocr-if-available.patch
> > http://userweb.kernel.org/~akpm/mmotm/broken-out/omap-hsmmc-do-not-enable-buffer-ready-interrupt-if-using-dma.patch
> > http://userweb.kernel.org/~akpm/mmotm/broken-out/mmc-msm_sdccc-driver-for-htc-dream.patch
> > http://userweb.kernel.org/~akpm/mmotm/broken-out/msm_sdccc-convert-printkkern_level-to-pr_level.patch
> > http://userweb.kernel.org/~akpm/mmotm/broken-out/msm_sdccc-stylistic-cleaning.patch
> > http://userweb.kernel.org/~akpm/mmotm/broken-out/msm_sdccc-move-overly-indented-code-to-separate-function.patch
> >
> > I guess we own them now ;)
>
> So how about, as an experiment, you put all those (at least those that are
> "stable") into a git tree (or quilt series) based on Linus' tree and I
> could replace the current linux-next mmc tree (which is empty) with that.
>
I haven't worked out how to do that yet :( (Well, I have, but it's all
complex).
It gets easy if I remove linux-next.patch from -mm. Maybe I'll do that.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists