From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-mtd@lists.infradead.org,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: [PATCH 1/2] mtd: Add NAND device drivers to MAINTAINERS
Date: Thu, 21 Nov 2013 16:11:18 -0300 [thread overview]
Message-ID: <20131121191117.GB3241@localhost> (raw)
In-Reply-To: <20131121185314.GK9468@ld-irv-0074.broadcom.com>
On Thu, Nov 21, 2013 at 10:53:14AM -0800, Brian Norris wrote:
> On Wed, Nov 20, 2013 at 09:20:08AM -0300, Ezequiel Garcia wrote:
> > Add drivers/mtd/nand/ to MAINTAINERS file with Brian Norris
> > as the subsystem maintainer.
> >
> > Cc: Brian Norris <computersforpeace@gmail.com>
> > Cc: David Woodhouse <dwmw2@infradead.org>
> > Signed-off-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
> > ---
> > MAINTAINERS | 12 ++++++++++++
> > 1 file changed, 12 insertions(+)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 167e188..d4145f7 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -5554,6 +5554,18 @@ F: drivers/mtd/
> > F: include/linux/mtd/
> > F: include/uapi/mtd/
> >
> > +NAND DEVICE DRIVERS
>
> While it would be nice for MTD and NAND to be listed together, I think
> this file is in alphabetical order ("NAND" doesn't come between "MTD"
> and "MEN").
>
Right, I haven't noticed order.
> Also, I might recommend including "FLASH" in the title: NAND FLASH
> DEVICE DRIVERS.
>
Sure...
> > +M: Brian Norris <computersforpeace@gmail.com>
> > +L: linux-mtd@lists.infradead.org
> > +W: http://www.linux-mtd.infradead.org/
> > +Q: http://patchwork.ozlabs.org/project/linux-mtd/list/
> > +T: git http://git.infradead.org/l2-mtd.git
>
> The git tree is an interesting case. l2-mtd.git was really only set up
> as a secondary tree, not as the official tree. It has moved to being the
> primary place for development, though, so your entry does reflect
> reality...
>
Maybe create a new git repository, specially for this?
> > +S: Maintained
> > +F: drivers/mtd/nand/
> > +F: include/linux/mtd/nand.h
> > +F: include/linux/mtd/nand_ecc.h
> > +F: include/linux/mtd/nand_bch.h
>
> include/linux/mtd/nand*.h?
> include/linux/mtd/bbm.h?
>
Yes, that's probably better.
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-11-21 19:11 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 [this message]
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
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=20131121191117.GB3241@localhost \
--to=ezequiel.garcia@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.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