From: Chris Ball <cjb@laptop.org>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Linus Walleij <linus.walleij@stericsson.com>,
linux-mmc@vger.kernel.org, Per Forlin <per.forlin@stericsson.com>,
Ulf Hansson <ulf.hansson@stericsson.com>,
Linus Walleij <linus.walleij@linaro.org>,
Pawel Moll <pawel.moll@arm.com>
Subject: Re: [PATCH] mmc: mmci: assume maintainership
Date: Mon, 09 Apr 2012 18:44:48 -0400 [thread overview]
Message-ID: <874nssy17j.fsf@laptop.org> (raw)
In-Reply-To: <20120315173047.GB17243@flint.arm.linux.org.uk> (Russell King's message of "Thu, 15 Mar 2012 17:30:47 +0000")
Hi Russell,
On Thu, Mar 15 2012, Russell King wrote:
> On Thu, Mar 15, 2012 at 03:30:36PM +0100, Linus Walleij wrote:
>> From: Linus Walleij <linus.walleij@linaro.org>
>>
>> So since this driver is crucial for us (as in ST-Ericsson)
>> to have actively maintained, and since it is marked orphaned
>> I will assume maintainership for it starting with the 3.5
>> integration cycle. The idea is to collect patches and send
>> either patch sets of pull requests to Chris.
>
> Actually, I still want to be involved because I'm far from convinced with
> some of the patches coming from Ulf are correct for ARMs implementation.
> That's why I'm purposely not applying the MMCI patches in the patch system
> in a particularly fast manner - I want there to be a decent amount of
> testing between each set of patches.
> [..]
> So, it's not really unmaintained or orphaned...
Please could you send a MAINTAINERS patch to Linus adding yourself for MMCI?
Thanks,
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
prev parent reply other threads:[~2012-04-09 22:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 14:30 [PATCH] mmc: mmci: assume maintainership Linus Walleij
2012-03-15 14:36 ` Ulf Hansson
2012-03-15 14:36 ` Per Förlin
2012-03-15 14:52 ` Pawel Moll
2012-03-15 17:30 ` Russell King
2012-03-15 17:42 ` Linus Walleij
2012-03-16 8:48 ` Ulf Hansson
2012-03-16 8:53 ` Russell King
2012-03-16 9:24 ` Ulf Hansson
2012-03-17 8:58 ` Russell King
2012-04-09 22:44 ` Chris Ball [this message]
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=874nssy17j.fsf@laptop.org \
--to=cjb@laptop.org \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-mmc@vger.kernel.org \
--cc=pawel.moll@arm.com \
--cc=per.forlin@stericsson.com \
--cc=rmk@arm.linux.org.uk \
--cc=ulf.hansson@stericsson.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.