From: Bjorn Helgaas <helgaas@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Thierry Reding <treding@nvidia.com>
Subject: [GIT PULL] PCI fixes for v4.14
Date: Fri, 13 Oct 2017 15:00:04 -0500 [thread overview]
Message-ID: <20171013200004.GA10475@bhelgaas-glaptop.roam.corp.google.com> (raw)
PCI fixes:
- revert Tegra MSI change that caused a regression on TrimSlice (Thierry
Reding)
- finish Aardvark conversion to host bridge IRQ mapping. We missed
Aardvark the first time around so it regressed (Thomas Petazzoni)
The following changes since commit b1f9e5e355e909000fcccfd2bc31f7c1ded358ab:
ide: fix IRQ assignment for PCI bus order probing (2017-10-03 14:03:31 -0500)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git tags/pci-v4.14-fixes-5
for you to fetch changes up to 407dae1e4415acde2d9f48bb76361893c4653756:
PCI: aardvark: Move to struct pci_host_bridge IRQ mapping functions (2017-10-10 21:17:43 -0500)
----------------------------------------------------------------
pci-v4.14-fixes-5
----------------------------------------------------------------
Thierry Reding (1):
Revert "PCI: tegra: Do not allocate MSI target memory"
Thomas Petazzoni (1):
PCI: aardvark: Move to struct pci_host_bridge IRQ mapping functions
drivers/pci/host/pci-aardvark.c | 2 ++
drivers/pci/host/pci-tegra.c | 22 ++++++----------------
2 files changed, 8 insertions(+), 16 deletions(-)
next reply other threads:[~2017-10-13 20:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 20:00 Bjorn Helgaas [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-11-09 23:58 Bjorn Helgaas
2017-10-27 20:17 Bjorn Helgaas
2017-10-06 18:50 Bjorn Helgaas
2017-09-29 19:08 Bjorn Helgaas
2017-09-22 14:04 Bjorn Helgaas
2017-09-16 2:59 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=20171013200004.GA10475@bhelgaas-glaptop.roam.corp.google.com \
--to=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=torvalds@linux-foundation.org \
--cc=treding@nvidia.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
all inboxes | Powered by JetHome®