How to handle patches that cross maintainers?

4 messages, 4 authors, 2007-07-03 · open the first message on its own page

How to handle patches that cross maintainers?

From: Kumar Gala <hidden>
Date: 2007-07-03 09:01:48

Andrew,

I was hoping to get your input on how to handle patches that cross  
maintainers.  I've got a patch that is pretty PPC specific, but  
happens to touch some drivers as well.

Here's the diffstat to get a rough idea:

arch/powerpc/kernel/io.c                |   12 ++++++------
arch/powerpc/mm/hash_native_64.c        |    2 +-
arch/powerpc/mm/stab.c                  |    4 ++--
drivers/ide/pci/scc_pata.c              |    4 ++--
drivers/media/dvb/bt8xx/bt878.h         |    5 ++---
drivers/serial/cpm_uart/cpm_uart_core.c |    2 +-
include/asm-powerpc/system.h            |    2 +-
7 files changed, 15 insertions(+), 16 deletions(-)

Now, I've had this issue before w/o any good sense on how to handle it.

Suggestions?

- k

Re: How to handle patches that cross maintainers?

From: Andrew Morton <akpm@linux-foundation.org>
Date: 2007-07-03 09:38:36

On Tue, 3 Jul 2007 04:01:20 -0500 Kumar Gala [off-list ref] wrote:
Andrew,

I was hoping to get your input on how to handle patches that cross  
maintainers.  I've got a patch that is pretty PPC specific, but  
happens to touch some drivers as well.

Here's the diffstat to get a rough idea:

arch/powerpc/kernel/io.c                |   12 ++++++------
arch/powerpc/mm/hash_native_64.c        |    2 +-
arch/powerpc/mm/stab.c                  |    4 ++--
drivers/ide/pci/scc_pata.c              |    4 ++--
drivers/media/dvb/bt8xx/bt878.h         |    5 ++---
drivers/serial/cpm_uart/cpm_uart_core.c |    2 +-
include/asm-powerpc/system.h            |    2 +-
7 files changed, 15 insertions(+), 16 deletions(-)

Now, I've had this issue before w/o any good sense on how to handle it.

Suggestions?
Well, assuming that all the changes are interdependent and cannot be split
up: send it to the relevant maintainers, gather the acks and merge it up
yourself.

Re: How to handle patches that cross maintainers?

From: Christoph Hellwig <hch@lst.de>
Date: 2007-07-03 14:14:57

On Tue, Jul 03, 2007 at 04:01:20AM -0500, Kumar Gala wrote:
Andrew,

I was hoping to get your input on how to handle patches that cross  
maintainers.  I've got a patch that is pretty PPC specific, but  
happens to touch some drivers as well.
I think the real question is why the heck does it touch those drivers?
:)

Re: How to handle patches that cross maintainers?

From: Mauro Carvalho Chehab <hidden>
Date: 2007-07-03 15:03:08

Em Ter, 2007-07-03 às 04:01 -0500, Kumar Gala escreveu:
Andrew,

I was hoping to get your input on how to handle patches that cross  
maintainers.  I've got a patch that is pretty PPC specific, but  
happens to touch some drivers as well.

Here's the diffstat to get a rough idea:

arch/powerpc/kernel/io.c                |   12 ++++++------
arch/powerpc/mm/hash_native_64.c        |    2 +-
arch/powerpc/mm/stab.c                  |    4 ++--
drivers/ide/pci/scc_pata.c              |    4 ++--
drivers/media/dvb/bt8xx/bt878.h         |    5 ++---
drivers/serial/cpm_uart/cpm_uart_core.c |    2 +-
include/asm-powerpc/system.h            |    2 +-
7 files changed, 15 insertions(+), 16 deletions(-)

Now, I've had this issue before w/o any good sense on how to handle it.
The better is to copy all of us and wait for some time to allow each
maintainer to ack or comment the changeset, if needed.

Please c/c me for any changes on /drivers/media stuff.

Cheers,
Mauro
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help