From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Gavin Shan <shangw@linux.vnet.ibm.com>
Cc: Yuanquan.Chen@freescale.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/pci: Avoid overriding MSI interrupt
Date: Sat, 29 Jun 2013 17:20:34 +1000 [thread overview]
Message-ID: <1372490434.18612.64.camel@pasglop> (raw)
In-Reply-To: <1372425030-5759-1-git-send-email-shangw@linux.vnet.ibm.com>
On Fri, 2013-06-28 at 21:10 +0800, Gavin Shan wrote:
> The issue was introduced by commit 37f02195 ("powerpc/pci: fix
> PCI-e devices rescan issue on powerpc platform"). The field
That "fix" caused more problems than it solved. There's a better
approach floating around that I will merge eventually next week.
Cheers,
Ben.
next prev parent reply other threads:[~2013-06-29 7:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 13:10 [PATCH] powerpc/pci: Avoid overriding MSI interrupt Gavin Shan
2013-06-29 7:20 ` Benjamin Herrenschmidt [this message]
2013-06-29 23:09 ` Benjamin Herrenschmidt
2013-06-30 1:29 ` Guenter Roeck
2013-06-30 1:51 ` Gavin Shan
2013-06-30 4:06 ` 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=1372490434.18612.64.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=Yuanquan.Chen@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=shangw@linux.vnet.ibm.com \
/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).