From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Mike Qiu <qiudayu@linux.vnet.ibm.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] PowerNV/PCI: Fix NULL PCI controller
Date: Tue, 23 Apr 2013 11:49:10 +1000 [thread overview]
Message-ID: <1366681750.2886.10.camel@pasglop> (raw)
In-Reply-To: <1366681602.1654.8.camel@localhost.localdomain>
On Mon, 2013-04-22 at 21:46 -0400, Mike Qiu wrote:
>
> So I suggest either use my patch or remove that check code.
> If the second case, I will write v2 patch to remove that check code.
> I don't know what's to go for next step, it depends on the
> maintainer :)
Please do.
Cheers,
Ben.
prev parent reply other threads:[~2013-04-23 1:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 6:13 [PATCH] PowerNV/PCI: Fix NULL PCI controller Mike Qiu
2013-04-22 6:15 ` Mike Qiu
2013-04-22 6:36 ` Benjamin Herrenschmidt
2013-04-22 7:41 ` Mike Qiu
2013-04-22 8:04 ` Benjamin Herrenschmidt
2013-04-22 9:44 ` Mike Qiu
2013-04-22 17:35 ` Bjorn Helgaas
2013-04-23 1:46 ` Mike Qiu
2013-04-23 1:49 ` 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=1366681750.2886.10.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=qiudayu@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
/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