linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: list <linuxppc-dev@ozlabs.org>,
	linuxppc-dev, Paul Mackerras <paulus@samba.org>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: How to handle patches that cross maintainers?
Date: Tue, 3 Jul 2007 02:38:05 -0700	[thread overview]
Message-ID: <20070703023805.f174b5b8.akpm@linux-foundation.org> (raw)
In-Reply-To: <4BEFAFC6-3346-4F29-B1C5-377952E3FBBF@kernel.crashing.org>

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.

  reply	other threads:[~2007-07-03  9:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-03  9:01 How to handle patches that cross maintainers? Kumar Gala
2007-07-03  9:38 ` Andrew Morton [this message]
2007-07-03 14:13 ` Christoph Hellwig
2007-07-03 15:01 ` Mauro Carvalho Chehab

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070703023805.f174b5b8.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=galak@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).