linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: <linux-mtd@lists.infradead.org>
Cc: Brian Norris <computersforpeace@gmail.com>,
	David Woodhouse <dwmw2@infradead.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
	Artem Bityutskiy <dedekind1@gmail.com>
Subject: [PATCH 0/2] MTD maintenance updates
Date: Wed,  4 Dec 2013 15:28:44 -0800	[thread overview]
Message-ID: <1386199726-28074-1-git-send-email-computersforpeace@gmail.com> (raw)

Hello all,

I'm taking up where Ezequiel left off on updating MAINTAINERS for MTD [1], with
the following changes:

 1. Get things in alphabetical order.

 2. I think I will be generally helping with all of MTD here, so rather than
    adding a new entry for NAND, just stick me under David Woodhouse. Of
    course, this doesn't quite make me an expert on all areas...

The second patch is just a trivial modification to Ezequiel's 2nd patch.

I agree with Ezequiel's suggestion, that we can assign driver maintainers for
ones that have a particular sense of ownership (e.g., a driver's author, or a
heavily-contributing developer for a driver), and I think this falls in line
with existing practice throughout the kernel. However, this isn't strictly
necessary; for some developers, de facto maintainership can suffice, with no
official role, and get_maintainers.pl pulls suggestions from recent
contribution history in git anyway. So I won't personally push hard for
assigning many driver maintainers.

BTW, I'd like to get David's "ack" for these patches, and it'd be nice to hear
from Artem too, since he has previously been an unofficial maintainer (and is
understandably distracted by non-MTD work these days).

Brian

[1] http://lists.infradead.org/pipermail/linux-mtd/2013-November/050122.html

Brian Norris (1):
  MAINTAINERS: mtd: add Brian Norris for MTD maintenance

Ezequiel Garcia (1):
  MAINTAINERS: mtd: add PXA3xx NAND driver to MAINTAINERS

 MAINTAINERS | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

-- 
1.8.5

             reply	other threads:[~2013-12-04 23:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-04 23:28 Brian Norris [this message]
2013-12-04 23:28 ` [PATCH 1/2] MAINTAINERS: mtd: add Brian Norris for MTD maintenance Brian Norris
2013-12-04 23:28 ` [PATCH v2 2/2] MAINTAINERS: mtd: add PXA3xx NAND driver to MAINTAINERS Brian Norris
2013-12-05  8:34 ` [PATCH 0/2] MTD maintenance updates Artem Bityutskiy
2013-12-14  5:54   ` Brian Norris

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=1386199726-28074-1-git-send-email-computersforpeace@gmail.com \
    --to=computersforpeace@gmail.com \
    --cc=dedekind1@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).