From: Marek Vasut <marex@denx.de>
To: Brian Norris <computersforpeace@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
David Woodhouse <dwmw2@infradead.org>,
"Gupta, Pekon" <pekon@ti.com>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: [PATCH 0/2] Regarding NAND core and drivers maintenance
Date: Wed, 27 Nov 2013 11:43:28 +0100 [thread overview]
Message-ID: <201311271143.28106.marex@denx.de> (raw)
In-Reply-To: <20131127030736.GW9468@ld-irv-0074.broadcom.com>
Hi Brian,
> On Fri, Nov 22, 2013 at 07:07:09AM +0000, Pekon Gupta wrote:
> > > My proposal (copy-pasted from the media subsystem) is to define
> > > sub-maintainers, one for each NAND driver, in addition to the top-level
> > > NAND subsystem maintainer.
> > >
> > > When a patch comes for a given driver, the _ideal_ situation would be
> > > for the sub-maintainer to Ack-it first.
> >
> > Specifically, we need someone to keep a watch on m25p80 (apart from
> > David and Brian). This is because I see lot of patches coming in but not
> > on generic framework approach. Serial Flash driver might be next big
> > component of MTD sub-system in coming times.
>
> Hmm, I don't know if we really need a separate SPI NOR maintainer, and I
> don't know if we have anyone with enough experience with SPI NOR to
> qualify anyway. I know Marek Vasut has been a good reviewer, but I'd be
> surprised if he really wanted to take official responsibility. And
> anyway, implementors and reviewers don't have to be official
> maintainers, so this shouldn't stop any pending work on the subject.
I'm honestly pleased by you saying this ;-) I don't mind continue reviewing, but
if things were to blow out of proportion, I don't mind helping either.
> Also, I have some HW that can do quad-SPI, but only in limited
> circumstances. Right now, my driver is just faking being a generic SPI
> driver when it really scrapes the commands and performs accelerated
> transactions on ones it recognizes... so it shares some similarities
> with what Huang is trying to do. I hope to contribute more to the
> generic framework of SPI NOR in the future (as time allows, of course).
>
> So while I might be officially responsible for driver/mtd/nand/, I will
> be involved in the rest of MTD and will likely continue to queue up
> patches anyway.
Thanks for that !
Best regards,
Marek Vasut
prev parent reply other threads:[~2013-11-27 10:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 12:20 [PATCH 0/2] Regarding NAND core and drivers maintenance Ezequiel Garcia
2013-11-20 12:20 ` [PATCH 1/2] mtd: Add NAND device drivers to MAINTAINERS Ezequiel Garcia
2013-11-21 18:53 ` Brian Norris
2013-11-21 19:11 ` Ezequiel Garcia
2013-11-27 3:20 ` Brian Norris
2013-11-20 12:20 ` [PATCH 2/2] mtd: Add PXA3xx NAND driver " Ezequiel Garcia
2013-11-21 18:45 ` [PATCH 0/2] Regarding NAND core and drivers maintenance Brian Norris
2013-11-22 7:07 ` Gupta, Pekon
2013-11-22 8:02 ` Huang Shijie
2013-11-27 3:07 ` Brian Norris
2013-11-27 10:43 ` Marek Vasut [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=201311271143.28106.marex@denx.de \
--to=marex@denx.de \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=ezequiel.garcia@free-electrons.com \
--cc=linux-mtd@lists.infradead.org \
--cc=pekon@ti.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.