mbox

[GIT,PULL] PCI fixes for v4.10

Message ID 20170202161812.GB21267@bhelgaas-glaptop.roam.corp.google.com
State Not Applicable
Headers show

Pull-request

git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git tags/pci-v4.10-fixes-2

Message

Bjorn Helgaas Feb. 2, 2017, 4:18 p.m. UTC
PCI fixes:

  - configure ASPM on the link from a PCI-to-PCIe bridge (avoids a NULL
    pointer dereference on topologies including these bridges)

The following changes since commit 4d191b1b63c209e37bf27938ef365244d3c41084:

  PCI/MSI: pci-xgene-msi: Fix CPU hotplug registration handling (2017-01-17 08:41:51 -0600)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git tags/pci-v4.10-fixes-2

for you to fetch changes up to 030305d69fc6963c16003f50d7e8d74b02d0a143:

  PCI/ASPM: Handle PCI-to-PCIe bridges as roots of PCIe hierarchies (2017-01-27 15:00:45 -0600)

----------------------------------------------------------------
pci-v4.10-fixes-2

----------------------------------------------------------------
Bjorn Helgaas (1):
      PCI/ASPM: Handle PCI-to-PCIe bridges as roots of PCIe hierarchies

 drivers/pci/pcie/aspm.c | 19 +++++++++++++------
 1 file changed, 13 insertions(+), 6 deletions(-)

Comments

Christoph Hellwig Feb. 2, 2017, 4:30 p.m. UTC | #1
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?
Bjorn Helgaas Feb. 2, 2017, 4:46 p.m. UTC | #2
On Thu, Feb 02, 2017 at 08:30:24AM -0800, Christoph Hellwig wrote:
> 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?

I assume you mean https://patchwork.ozlabs.org/patch/721415/

I just hadn't gotten to that one.  I hadn't read the description carefully
enough to see that it needed to go in v4.10.