Skip to contentSkip to conversation

MAINTAINERS: add SPI co-maintainer.

RFC In review Grant Likely 1 participant 2 messages Nov 14, 2009 – Nov 20, 2009 SPI

lore
Share & tools
lore
#0 lore raw

RFC 1/1 MAINTAINERS: add SPI co-maintainer.

---

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(-)
MAINTAINERS +1 -0
index a1a2ace..2b697cb 100644
@@ -4937,6 +4937,7 @@ F:	drivers/char/specialix*
 
 SPI SUBSYSTEM
 M:	David Brownell <[email protected]>
+M:	Grant Likely <[email protected]>
 L:	[email protected]
 S:	Maintained
 F:	Documentation/spi/
#1 lore raw

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.

Quoted 42 lines · Grant Likely

---

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(-)
MAINTAINERS +0 -0
index a1a2ace..2b697cb 100644
@@ -4937,6 +4937,7 @@ F:        drivers/char/specialix*
 

 SPI SUBSYSTEM
 M:     David Brownell <[email protected]> +M:     Grant Likely <[email protected]>
 L:     [email protected]
 S:     Maintained
 F:     Documentation/spi/

Signature · 2 lines
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.