From: Cyrille Pitchen <cyrille.pitchen@atmel.com>
To: Richard Weinberger <richard.weinberger@gmail.com>,
Marek Vasut <marex@denx.de>
Cc: Brian Norris <computersforpeace@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
<nicolas.ferre@atmel.com>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] MAINTAINERS: add a maintainer for the SPI NOR subsystem
Date: Tue, 18 Oct 2016 17:55:23 +0200 [thread overview]
Message-ID: <3d45f698-08e9-e672-d405-1ab9bfec1222@atmel.com> (raw)
In-Reply-To: <CAFLxGvy9okx1cHnRhq2U-u574PzAk=Tampw1Fmvp4KzY8vnDnw@mail.gmail.com>
Le 18/10/2016 à 17:30, Richard Weinberger a écrit :
> On Tue, Oct 18, 2016 at 5:17 PM, Marek Vasut <marex@denx.de> wrote:
>> On 10/18/2016 04:58 PM, Cyrille Pitchen wrote:
>>> I would like to volunteer as a maintainer for the SPI NOR part of the MTD
>>> subsystem.
>>>
>>> Over the last months, a significant number of SPI NOR related patches have
>>> been submitted, some of them have been reviewed, but very few have finally
>>> been merged. Hence, the number of pending SPI NOR related patches continues
>>> to increase over the time.
>>>
>>> Through my work on SPI NOR memories from many manufacturers over the last
>>> two years, I've gained a solid understanding of this technology.
>>> I've already helped by reviewing patches from other contributors on the
>>> mailing list, and would like to help getting those patches integrated by
>>> volunteering as a maintainer for this specific area.
>>>
>>> Boris Brezillon has already stepped up as a maintainer for the NAND
>>> sub-subsystem in MTD, and the SPI NOR sub-subsystem could be handled in
>>> the same way: I would be reviewing patches touching this area, collecting
>>> them and sending pull requests to Brian Norris.
>
> I'd suggest you send pull requests directly to Linus.
> Same for NAND.
>
>>> Signed-off-by: Cyrille Pitchen <cyrille.pitchen@atmel.com>
>>
>> Let me know if you need co-maintainer.
>
> +1
>
> While we are here, what about forming a MTD maintainer team?
> This concept works very well for other subsystems.
>
I totally agree with you so if Marek and you volunteer as well, your help
will be precious!
next prev parent reply other threads:[~2016-10-18 15:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 14:58 Cyrille Pitchen
2016-10-18 15:17 ` Marek Vasut
2016-10-18 15:30 ` Richard Weinberger
2016-10-18 15:55 ` Cyrille Pitchen [this message]
2016-10-18 16:15 ` Richard Weinberger
2016-10-18 16:37 ` Marek Vasut
2016-10-18 18:46 ` Brian Norris
2016-10-18 19:02 ` Richard Weinberger
2016-10-18 19:15 ` Boris Brezillon
2016-10-18 21:10 ` David Oberhollenzer
2016-10-18 22:04 ` Marek Vasut
2016-10-18 19:31 ` Marek Vasut
2016-10-18 19:41 ` Boris Brezillon
2016-10-18 19:51 ` Marek Vasut
2016-10-19 6:41 ` Artem Bityutskiy
2016-10-18 19:59 ` Moritz Fischer
2016-10-18 20:18 ` Richard Weinberger
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=3d45f698-08e9-e672-d405-1ab9bfec1222@atmel.com \
--to=cyrille.pitchen@atmel.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marex@denx.de \
--cc=nicolas.ferre@atmel.com \
--cc=richard.weinberger@gmail.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
all inboxes | Powered by JetHome®