From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Ayman El-Khashab <AymanE@tanisys.com>
Cc: linuxppc-dev@ozlabs.org, linux-pci@vger.kernel.org
Subject: RE: [RFC/PATCH] pci: Workaround invalid P2P bridge bus numbers
Date: Wed, 22 Oct 2008 09:33:00 +1100 [thread overview]
Message-ID: <1224628380.7654.277.camel@pasglop> (raw)
In-Reply-To: <16691A8B34B5D9458EA3A1C37A11555A0137F833@tanisys-ex2.Tanisys.Local>
On Tue, 2008-10-21 at 09:36 -0500, Ayman El-Khashab wrote:
> > Ayman, can you double check that this variant of the patch still
> > fixes your problem ? Thanks !
> >
>
> I've tried it out and it is working correctly with my devices. The
> subordinate bus numbers on all the ports are correct.
Thanks !
Cheers,
Ben.
next prev parent reply other threads:[~2008-10-21 22:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 23:06 [RFC/PATCH] pci: Workaround invalid P2P bridge bus numbers Benjamin Herrenschmidt
2008-10-20 23:17 ` Jesse Barnes
2008-10-21 14:36 ` Ayman El-Khashab
2008-10-21 22:33 ` Benjamin Herrenschmidt [this message]
2008-10-21 22:58 ` Jesse Barnes
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=1224628380.7654.277.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=AymanE@tanisys.com \
--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).