* [RFC] MAINTAINERS: add SPI co-maintainer.
@ 2009-11-14 0:25 Grant Likely
2009-11-20 18:01 ` Grant Likely
0 siblings, 1 reply; 2+ messages in thread
From: Grant Likely @ 2009-11-14 0:25 UTC (permalink / raw)
To: akpm, dbrownell, spi-devel-general, linux-kernel
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/
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [RFC] MAINTAINERS: add SPI co-maintainer.
2009-11-14 0:25 [RFC] MAINTAINERS: add SPI co-maintainer Grant Likely
@ 2009-11-20 18:01 ` Grant Likely
0 siblings, 0 replies; 2+ messages in thread
From: Grant Likely @ 2009-11-20 18:01 UTC (permalink / raw)
To: akpm, dbrownell, spi-devel-general, linux-kernel, Stephen Rothwell
Ping? Any comments on this?
If I don't hear anything, then I think I'm going to go ahead and push
out a tree with all the SPI changes I've signed off on and ask sfr to
add it to his list, just so that I'm sure that they get some
linux-next exposure before Linus opens the merge window. I won't
necessarily ask LInus to pull it, I just want the testing.
Cheers.
g.
On Fri, Nov 13, 2009 at 5:25 PM, Grant Likely <grant.likely@secretlab.ca> wrote:
> 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/
>
>
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-11-20 18:01 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-11-14 0:25 [RFC] MAINTAINERS: add SPI co-maintainer Grant Likely
2009-11-20 18:01 ` Grant Likely
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).