From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Greg KH <greg@kroah.com>
Cc: Michael Ellerman <michael@ellerman.id.au>,
Andrew Morton <akpm@osdl.org>,
PPC64-dev <linuxppc64-dev@ozlabs.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH] Updated: fix-pci-mmap-on-ppc-and-ppc64.patch
Date: Sat, 14 May 2005 09:29:32 +1000 [thread overview]
Message-ID: <1116026972.5128.29.camel@gaston> (raw)
In-Reply-To: <20050513161855.GC11089@kroah.com>
On Fri, 2005-05-13 at 09:18 -0700, Greg KH wrote:
> On Fri, May 13, 2005 at 05:44:10PM +1000, Michael Ellerman wrote:
> > Hi Andrew,
>
> Hm, why not send this to the pci maintainer?
Because I told him to send it to Andrew as it's just an arch bugfix on
top of my patch that is already in mm ;)
> I'll add it to my queue.
Thanks,
Ben.
prev parent reply other threads:[~2005-05-13 23:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 7:44 [PATCH] Updated: fix-pci-mmap-on-ppc-and-ppc64.patch Michael Ellerman
2005-05-13 7:59 ` Benjamin Herrenschmidt
2005-05-13 16:18 ` Greg KH
2005-05-13 23:29 ` Benjamin Herrenschmidt [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=1116026972.5128.29.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=linuxppc64-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
/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