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>,
Rob Herring <robh@kernel.org>,
vtolkm@googlemail.com, Vidya Sagar <vidyas@nvidia.com>,
Boris V <borisvk@bstnet.org>, Rajat Jain <rajatja@google.com>
Subject: [GIT PULL] PCI fixes for v5.10
Date: Wed, 4 Nov 2020 15:10:33 -0600 [thread overview]
Message-ID: <20201104211033.GA418499@bjorn-Precision-5520> (raw)
The following changes since commit 3650b228f83adda7e5ee532e2b90429c03f7b9ec:
Linux 5.10-rc1 (2020-10-25 15:14:11 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git tags/pci-v5.10-fixes-1
for you to fetch changes up to 832ea234277a2465ec6602fa6a4db5cd9ee87ae3:
PCI: mvebu: Fix duplicate resource requests (2020-11-04 13:55:30 -0600)
----------------------------------------------------------------
PCI fixes:
- Fix ACS regression that broke device pass-through (Rajat Jain)
- Revert DesignWare ATU memory resource to use last entry to fix Tegra194
regression (Rob Herring)
- Remove duplicate mvebu resource requests to fix regression on Turris
Omnia (Rob Herring)
----------------------------------------------------------------
Rajat Jain (1):
PCI: Always enable ACS even if no ACS Capability
Rob Herring (2):
PCI: dwc: Restore ATU memory resource setup to use last entry
PCI: mvebu: Fix duplicate resource requests
drivers/pci/controller/dwc/pcie-designware-host.c | 8 ++++++--
drivers/pci/controller/pci-mvebu.c | 23 ++++++++++-------------
drivers/pci/pci.c | 9 +++++++--
3 files changed, 23 insertions(+), 17 deletions(-)
next reply other threads:[~2020-11-04 21:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 21:10 Bjorn Helgaas [this message]
2020-11-05 20:21 ` pr-tracker-bot
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=20201104211033.GA418499@bjorn-Precision-5520 \
--to=helgaas@kernel.org \
--cc=borisvk@bstnet.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=rajatja@google.com \
--cc=robh@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vidyas@nvidia.com \
--cc=vtolkm@googlemail.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®