From: Andrew Morton <akpm@linux-foundation.org>
To: Chris Ball <cjb@laptop.org>
Cc: linux-mmc@vger.kernel.org
Subject: Re: MMC maintainer
Date: Thu, 9 Sep 2010 11:47:50 -0700 [thread overview]
Message-ID: <20100909114750.09214854.akpm@linux-foundation.org> (raw)
In-Reply-To: <m3lj7avpk4.fsf@pullcord.laptop.org>
On Thu, 09 Sep 2010 12:39:55 -0400 Chris Ball <cjb@laptop.org> wrote:
> Hi all,
>
> I've been considering volunteering to take over as MMC maintainer.
> I mentioned this to my boss at OLPC, and he's willing to have some
> of my OLPC hours each week allocated towards maintaining MMC, which
> encourages me more.
>
> So, here's my humble offer: I can take care of maintaining an MMC tree
> for -next, keeping it working and tested, sending pull requests, and
> making sure that patches are kept track of and reach the appropriate
> places for review. I wouldn't plan on changing patch workflow --
> patches would still be submitted and responded to on the list.
>
> I'm also interested in setting up automated testing to catch
> performance and functionality regressions similarly to the Xorg
> Tinderbox__, which I run. Aside from that, I'd be open to hearing
> about what anyone else thinks is a priority to work on in the MMC
> stack.
>
> Let me know what you think,
Sounds good to me, thanks.
> and if this sounds like a reasonable
> idea then I'll work out a transition plan with Andrew.
These things can happen in parallel - get the tree set up, get it into
linux-next, start putting patches in it. If I see patches turn up in
linux-next which I already have, I just drop them. If I find I'm
holding patches which should be in the mmc tree but which aren't, I
send them to you.
next prev parent reply other threads:[~2010-09-09 18:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-09 16:39 MMC maintainer Chris Ball
2010-09-09 18:47 ` Andrew Morton [this message]
2010-09-10 20:14 ` Chris Ball
2010-09-10 20:58 ` Andrew Morton
2010-09-09 22:44 ` Nicolas Pitre
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=20100909114750.09214854.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cjb@laptop.org \
--cc=linux-mmc@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