From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Andrew Morton <akpm@linux-foundation.org>,
Paul Mackerras <paulus@samba.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: How to handle patches that cross maintainers?
Date: Tue, 03 Jul 2007 12:01:50 -0300 [thread overview]
Message-ID: <1183474910.3926.134.camel@gaivota> (raw)
In-Reply-To: <4BEFAFC6-3346-4F29-B1C5-377952E3FBBF@kernel.crashing.org>
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
prev parent reply other threads:[~2007-07-03 15:02 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
2007-07-03 14:13 ` Christoph Hellwig
2007-07-03 15:01 ` Mauro Carvalho Chehab [this message]
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=1183474910.3926.134.camel@gaivota \
--to=mchehab@infradead.org \
--cc=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