From: Grant Likely <grant.likely@linaro.org>
To: linux-kernel@vger.kernel.org
Cc: Grant Likely <grant.likely@linaro.org>,
Linux Walleij <linus.walleij@linaro.org>,
Mark Brown <broonie@kernel.org>,
Rob Herring <rob.herring@calxeda.com>
Subject: [PATCH 1/3] MAINTAINERS: Remove Grant Likely
Date: Fri, 19 Jul 2013 20:19:46 -0700 [thread overview]
Message-ID: <1374290388-19308-1-git-send-email-grant.likely@linaro.org> (raw)
Unfortunately, I'm no longer to spend the time needed on maintainership.
It is time for me to step aside and pass maintainership to other
engineers. I'm not disappearing from Linux development, but it would be
irresponsible for me to hold onto a job that I am unable to do.
v2: Leave my name on devicetree core code maintainership. Rob NAKed that
part of the patch. :)
Signed-off-by: Grant Likely <grant.likely@linaro.org>
Cc: Linux Walleij <linus.walleij@linaro.org>
Cc: Mark Brown <broonie@kernel.org>
Cc: Rob Herring <rob.herring@calxeda.com>
---
MAINTAINERS | 5 -----
1 file changed, 5 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index bf61e04..844d7e8 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3622,11 +3622,9 @@ F: drivers/isdn/gigaset/
F: include/uapi/linux/gigaset_dev.h
GPIO SUBSYSTEM
-M: Grant Likely <grant.likely@linaro.org>
M: Linus Walleij <linus.walleij@linaro.org>
S: Maintained
L: linux-gpio@vger.kernel.org
-T: git git://git.secretlab.ca/git/linux-2.6.git
F: Documentation/gpio.txt
F: drivers/gpio/
F: include/linux/gpio*
@@ -4472,8 +4470,6 @@ F: drivers/irqchip/
IRQ DOMAINS (IRQ NUMBER MAPPING LIBRARY)
M: Benjamin Herrenschmidt <benh@kernel.crashing.org>
-M: Grant Likely <grant.likely@linaro.org>
-T: git git://git.secretlab.ca/git/linux-2.6.git irqdomain/next
S: Maintained
F: Documentation/IRQ-domain.txt
F: include/linux/irqdomain.h
@@ -7746,7 +7742,6 @@ F: drivers/clk/spear/
SPI SUBSYSTEM
M: Mark Brown <broonie@kernel.org>
-M: Grant Likely <grant.likely@linaro.org>
L: linux-spi@vger.kernel.org
T: git git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
Q: http://patchwork.kernel.org/project/spi-devel-general/list/
--
1.8.1.2
next reply other threads:[~2013-07-20 12:23 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-20 3:19 Grant Likely [this message]
2013-07-20 3:19 ` [PATCH 2/3] MAINTAINERS: Change device tree mailing list Grant Likely
2013-07-20 3:19 ` [PATCH 3/3] MAINTAINERS: Refactor device tree maintainership Grant Likely
2013-07-20 16:20 ` Linus Walleij
2013-07-21 13:46 ` Jon Loeliger
2013-07-22 0:33 ` Grant Likely
2013-07-22 1:27 ` David Gibson
2013-07-22 17:38 ` Jon Loeliger
2013-07-21 0:17 ` Olof Johansson
2013-07-21 0:29 ` Joe Perches
2013-07-21 9:46 ` Grant Likely
2013-07-22 0:36 ` Grant Likely
2013-07-22 0:43 ` Joe Perches
2013-07-22 0:48 ` Grant Likely
2013-07-22 17:29 ` Olof Johansson
2013-07-21 18:56 ` Rob Herring
2013-07-22 0:35 ` Grant Likely
2013-07-22 20:31 ` Rob Herring
2013-07-22 21:36 ` Jon Loeliger
2013-07-23 3:27 ` Rob Herring
2013-07-22 16:50 ` Pawel Moll
2013-07-22 20:03 ` Rob Herring
2013-07-23 17:14 ` Pawel Moll
2013-07-23 17:59 ` Stephen Warren
2013-07-23 18:09 ` Ian Campbell
2013-07-23 18:44 ` Rob Herring
2013-07-23 18:55 ` Ian Campbell
2013-07-23 19:28 ` Rob Herring
2013-07-23 19:53 ` Stephen Warren
2013-08-07 10:53 ` Ian Campbell
2013-07-23 19:26 ` Nicolas Pitre
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=1374290388-19308-1-git-send-email-grant.likely@linaro.org \
--to=grant.likely@linaro.org \
--cc=broonie@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.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®