From: Christoph Hellwig <hch@lst.de>
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, 3 Jul 2007 16:13:51 +0200 [thread overview]
Message-ID: <20070703141351.GB18565@lst.de> (raw)
In-Reply-To: <4BEFAFC6-3346-4F29-B1C5-377952E3FBBF@kernel.crashing.org>
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?
:)
next prev parent reply other threads:[~2007-07-03 14:14 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 [this message]
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=20070703141351.GB18565@lst.de \
--to=hch@lst.de \
--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;
as well as URLs for NNTP newsgroup(s).