From: Grant Likely <grant.likely@secretlab.ca>
To: akpm@linux-foundation.org, dbrownell@users.sourceforge.net,
spi-devel-general@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: [RFC] MAINTAINERS: add SPI co-maintainer.
Date: Fri, 13 Nov 2009 17:25:45 -0700 [thread overview]
Message-ID: <20091114001001.5343.99566.stgit@angua> (raw)
Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
---
Hi David, Andrew.
David, I know that you haven't had enough time lately to keep on top
of the pending SPI patches, so I was wondering if you would like some
help? If you are interested, I'm willing to act as co-maintainer of
for the SPI subsystem.
Here's what I'm thinking. Right now all SPI patches are going through
the -mm tree and just adding to akpm's burden. I'd be more than happy
to take over the task of actually collecting the acked patches into a
git tree, getting them some exposure on linux-next, and asking Linus
to pull it during the merge window. If you ack them, then I'll merge
them.
I'm also be willing to take responsibility for all powerpc-specific
SPI patches so that you don't need to look at them.
How does this sound to you?
Cheers,
g.
MAINTAINERS | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index a1a2ace..2b697cb 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -4937,6 +4937,7 @@ F: drivers/char/specialix*
SPI SUBSYSTEM
M: David Brownell <dbrownell@users.sourceforge.net>
+M: Grant Likely <grant.likely@secretlab.ca>
L: spi-devel-general@lists.sourceforge.net
S: Maintained
F: Documentation/spi/
next reply other threads:[~2009-11-14 0:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-14 0:25 Grant Likely [this message]
2009-11-20 18:01 ` [RFC] MAINTAINERS: add SPI co-maintainer Grant Likely
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=20091114001001.5343.99566.stgit@angua \
--to=grant.likely@secretlab.ca \
--cc=akpm@linux-foundation.org \
--cc=dbrownell@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=spi-devel-general@lists.sourceforge.net \
/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).