From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: linuxppc-dev@ozlabs.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH] powerpc: Add legacy PCI access via sysfs
Date: Sat, 11 Oct 2008 10:19:45 +1100 [thread overview]
Message-ID: <1223680785.8157.168.camel@pasglop> (raw)
In-Reply-To: <200810100902.30191.jbarnes@virtuousgeek.org>
On Fri, 2008-10-10 at 09:02 -0700, Jesse Barnes wrote:
> Ah I was worried the first one might need a respin, but it applied
> fine, so
> I'll go ahead and apply this one too.
Let's hope it doesn't collide with the pending powerpc.git merge...
Ben.
next prev parent reply other threads:[~2008-10-10 23:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-10 2:50 [PATCH] powerpc: Add legacy PCI access via sysfs Benjamin Herrenschmidt
2008-10-10 16:02 ` Jesse Barnes
2008-10-10 23:19 ` Benjamin Herrenschmidt [this message]
2008-10-10 17:39 ` Jesse Barnes
2008-10-13 14:07 ` Josh Boyer
2008-10-13 17:29 ` Jesse Barnes
2008-10-13 23:39 ` Benjamin Herrenschmidt
2008-10-14 0:32 ` Benjamin Herrenschmidt
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=1223680785.8157.168.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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).