Remove me from maintainers for serial and mmc
PATCH 1/1 Remove me from maintainers for serial and mmc
As advertised earlier. I invite interested parties to take over and add their own entries as they see fit.
--- MAINTAINERS | 8 ++------ 1 files changed, 2 insertions(+), 6 deletions(-)
MAINTAINERS +2 -6
@@ -144,11 +144,9 @@ L: [email protected] S: Maintained 8250/16?50 (AND CLONE UARTS) SERIAL DRIVER -P: Russell King -M: [email protected] L: [email protected] W: http://serial.sourceforge.net -S: Maintained +S: Orphan 8390 NETWORK DRIVERS [WD80x3/SMC-ELITE, SMC-ULTRA, NE2000, 3C503, etc.] P: Paul Gortmaker
@@ -2003,9 +2001,7 @@ W: http://www.atnf.csiro.au/~rgooch/linu S: Maintained MULTIMEDIA CARD (MMC) SUBSYSTEM -P: Russell King -M: [email protected] -S: Maintained +S: Orphan MULTISOUND SOUND DRIVER P: Andrew Veliath
Signature · 3 lines
Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: 2.6 Serial core
Quoted 4 lines · Russell King
As advertised earlier. I invite interested parties to take over and add their own entries as they see fit.
Signed-off-by Russell King <[email protected]>
I don't know the formal process, but I am willing to take over the maintainership of MMC. This has been discussed, somewhat casually, in the last couple of weeks and I haven't seen any objections so far. :)
Rgds
Pierre
Quoted 10 lines · On Wed, 11 Oct 2006 16:16:39 +0200 Pierre Ossman <[email protected]> wrote:
Quoted 4 lines · Russell King
As advertised earlier. I invite interested parties to take over and add their own entries as they see fit.
Signed-off-by Russell King <[email protected]>I don't know the formal process, but I am willing to take over the maintainership of MMC. This has been discussed, somewhat casually, in the last couple of weeks and I haven't seen any objections so far. :)
Thanks. Please send a MAINTAINERS patch.
Quoted 2 lines · Andrew Morton
Thanks. Please send a
MAINTAINERSpatch.
Some practical questions for my new role. I intend to set up a public git repository (preferably on kernel.org, but I don't currently know the criteria there) as a means to expose my patches.
Quoted 1 line
From what I've observed, the work flow is something like this:
Have a "for-andrew" and a "for-linus" branch, depending on stuff for -mm or the main tree. Moving stuff between the two will be done in my rep and after which I send pull requests to LKML.
This might be a misunderstanding on my part, or for other reasons, not a way you wish to work. So I'm open to input on how I should structure things.
Rgds
Pierre
Quoted 7 lines · On Wed, 11 Oct 2006 20:15:56 +0200 Pierre Ossman <[email protected]> wrote:
Quoted 2 lines · Andrew Morton
Thanks. Please send a
MAINTAINERSpatch.Some practical questions for my new role. I intend to set up a public git repository (preferably on kernel.org, but I don't currently know the criteria there) as a means to expose my patches.
Send request to the nice people at [email protected]. gpg keys will be needed. See http://www.kernel.org/faq/#account
Quoted 8 lines
Quoted 1 line
From what I've observed, the work flow is something like this:
Have a "for-andrew" and a "for-linus" branch, depending on stuff for -mm or the main tree. Moving stuff between the two will be done in my rep and after which I send pull requests to LKML.
This might be a misunderstanding on my part, or for other reasons, not a way you wish to work. So I'm open to input on how I should structure things.
That's all ideal - go for it.