From: Christoph Hellwig <hch@infradead.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
lists@ssl-mail.com, "Jayachandran C." <jnair@caviumnetworks.com>,
"H.J. Lu" <hjl.tools@gmail.com>, Takashi Iwai <tiwai@suse.com>
Subject: Re: [GIT PULL] PCI fixes for v4.10
Date: Thu, 2 Feb 2017 08:30:24 -0800 [thread overview]
Message-ID: <20170202163024.GA30074@infradead.org> (raw)
In-Reply-To: <20170202161812.GB21267@bhelgaas-glaptop.roam.corp.google.com>
On Thu, Feb 02, 2017 at 10:18:12AM -0600, Bjorn Helgaas wrote:
> PCI fixes:
>
> - configure ASPM on the link from a PCI-to-PCIe bridge (avoids a NULL
> pointer dereference on topologies including these bridges)
Any reason you didn't include the affinity use outside the allocate
range fix sent on Tuesday?
next prev parent reply other threads:[~2017-02-02 16:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 16:18 [GIT PULL] PCI fixes for v4.10 Bjorn Helgaas
2017-02-02 16:30 ` Christoph Hellwig [this message]
2017-02-02 16:46 ` Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
2017-02-16 14:51 Bjorn Helgaas
[not found] <20170208192054.GA31395@bhelgaas-glaptop.roam.corp.google.com>
2017-02-08 19:22 ` Bjorn Helgaas
2017-02-09 4:06 ` Lukas Wunner
2017-02-09 15:09 ` Bjorn Helgaas
2017-02-09 18:23 ` Raj, Ashok
2017-02-09 18:46 ` Raj, Ashok
2017-05-02 1:54 ` Lukas Wunner
2017-05-02 2:41 ` Sinan Kaya
2017-05-02 10:49 ` Lukas Wunner
2017-05-02 14:15 ` Sinan Kaya
2017-05-02 18:48 ` Bjorn Helgaas
2017-05-03 18:04 ` Raj, Ashok
2017-05-06 9:04 ` Lukas Wunner
2017-02-09 20:11 ` Bjorn Helgaas
2017-02-10 12:39 ` Rafael J. Wysocki
2017-02-11 2:39 ` Yinghai Lu
2017-02-11 7:13 ` Yinghai Lu
2017-02-12 19:05 ` Lukas Wunner
2017-02-13 12:10 ` Rafael J. Wysocki
2017-01-19 14:27 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=20170202163024.GA30074@infradead.org \
--to=hch@infradead.org \
--cc=helgaas@kernel.org \
--cc=hjl.tools@gmail.com \
--cc=jnair@caviumnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lists@ssl-mail.com \
--cc=tiwai@suse.com \
--cc=torvalds@linux-foundation.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).