LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* How to handle patches that cross maintainers?
@ 2007-07-03  9:01 Kumar Gala
  2007-07-03  9:38 ` Andrew Morton
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: Kumar Gala @ 2007-07-03  9:01 UTC (permalink / raw)
  To: Andrew Morton; +Cc: Linux Kernel Development, linuxppc-dev list, Paul Mackerras

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: How to handle patches that cross maintainers?
  2007-07-03  9:01 How to handle patches that cross maintainers? Kumar Gala
@ 2007-07-03  9:38 ` Andrew Morton
  2007-07-03 14:13 ` Christoph Hellwig
  2007-07-03 15:01 ` Mauro Carvalho Chehab
  2 siblings, 0 replies; 4+ messages in thread
From: Andrew Morton @ 2007-07-03  9:38 UTC (permalink / raw)
  To: Kumar Gala; +Cc: Linux Kernel Development, linuxppc-dev list, Paul Mackerras

On Tue, 3 Jul 2007 04:01:20 -0500 Kumar Gala <galak@kernel.crashing.org> 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.


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: How to handle patches that cross maintainers?
  2007-07-03  9:01 How to handle patches that cross maintainers? Kumar Gala
  2007-07-03  9:38 ` Andrew Morton
@ 2007-07-03 14:13 ` Christoph Hellwig
  2007-07-03 15:01 ` Mauro Carvalho Chehab
  2 siblings, 0 replies; 4+ messages in thread
From: Christoph Hellwig @ 2007-07-03 14:13 UTC (permalink / raw)
  To: Kumar Gala
  Cc: Andrew Morton, linuxppc-dev list, Paul Mackerras,
	Linux Kernel Development

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?
:)


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: How to handle patches that cross maintainers?
  2007-07-03  9:01 How to handle patches that cross maintainers? Kumar Gala
  2007-07-03  9:38 ` Andrew Morton
  2007-07-03 14:13 ` Christoph Hellwig
@ 2007-07-03 15:01 ` Mauro Carvalho Chehab
  2 siblings, 0 replies; 4+ messages in thread
From: Mauro Carvalho Chehab @ 2007-07-03 15:01 UTC (permalink / raw)
  To: Kumar Gala
  Cc: Andrew Morton, Linux Kernel Development, linuxppc-dev list,
	Paul Mackerras

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


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2007-07-03 15:03 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-07-03  9:01 How to handle patches that cross maintainers? Kumar Gala
2007-07-03  9:38 ` Andrew Morton
2007-07-03 14:13 ` Christoph Hellwig
2007-07-03 15:01 ` Mauro Carvalho Chehab

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).