From: Linus Torvalds <torvalds@linux-foundation.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Rajat Jain <rajatxjain@gmail.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Rajat Jain <rajatjain@juniper.net>,
Guenter Roeck <groeck@juniper.net>,
Richard Yang <weiyang@linux.vnet.ibm.com>,
Matthew Wilcox <matthew.r.wilcox@intel.com>,
Yinghai Lu <yinghai@kernel.org>,
Josh Logan <joshtlogan@gmail.com>
Subject: Re: [PATCH] pci/probe: Enable CRS for Intel Haswell root ports
Date: Sat, 6 Sep 2014 16:28:27 -0700 [thread overview]
Message-ID: <CA+55aFxyjLKCr6xpYWtXW34_Z3v1_V2WB1vD583mAcPtGijn9A@mail.gmail.com> (raw)
In-Reply-To: <CAErSpo57EyJj1uc+oqvmy+_10AwwhrOQEO=EQbB2zs-7gd9tFA@mail.gmail.com>
On Sat, Sep 6, 2014 at 2:21 PM, Bjorn Helgaas <bhelgaas@google.com> wrote:
>
> But as you point out, we don't see the "not responding" message. We
> only print that if we read 0xffff0001 (device/vendor ID). But lspci
> claims the vendor:device ID is 0001:8168. So my new theory is:
[snip]
Sounds like a very reasonable theory and quite possible. And if Josh
actually still has the hardware, it would be lovely to hear the
results. Josh?
Linus
next prev parent reply other threads:[~2014-09-06 23:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 21:55 [PATCH] pci/probe: Enable CRS for Intel Haswell root ports Rajat Jain
2014-08-29 4:04 ` Wei Yang
2014-08-29 17:11 ` Rajat Jain
2014-08-31 13:31 ` Wei Yang
2014-09-02 4:14 ` Bjorn Helgaas
2014-09-02 18:39 ` Rajat Jain
2014-09-02 19:30 ` Linus Torvalds
2014-09-06 21:21 ` Bjorn Helgaas
2014-09-06 23:28 ` Linus Torvalds [this message]
2014-09-02 23:26 ` [PATCH v2] pci/probe: Enable CRS for root port if it is supported Rajat Jain
2014-09-09 5:38 ` Bjorn Helgaas
2014-09-09 18:35 ` Rajat Jain
2014-09-16 5:10 ` Rajat Jain
2014-09-16 15:40 ` Bjorn Helgaas
2014-09-22 18:54 ` Bjorn Helgaas
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=CA+55aFxyjLKCr6xpYWtXW34_Z3v1_V2WB1vD583mAcPtGijn9A@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=bhelgaas@google.com \
--cc=groeck@juniper.net \
--cc=joshtlogan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew.r.wilcox@intel.com \
--cc=rajatjain@juniper.net \
--cc=rajatxjain@gmail.com \
--cc=weiyang@linux.vnet.ibm.com \
--cc=yinghai@kernel.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).