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>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Guchun Chen" <guchun.chen@amd.com>,
"Pali Rohár" <pali@kernel.org>, "Jan Palus" <jpalus@fastmail.com>,
"Marcel Menzel" <mail@mcl.gg>,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] PCI fixes for v5.17
Date: Thu, 24 Feb 2022 13:56:11 -0600 [thread overview]
Message-ID: <20220224195611.GA289605@bhelgaas> (raw)
The following changes since commit e783362eb54cd99b2cac8b3a9aeac942e6f6ac07:
Linux 5.17-rc1 (2022-01-23 10:12:53 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git tags/pci-v5.17-fixes-5
for you to fetch changes up to 3f1271b54edcc692da5a3663f2aa2a64781f9bc3:
PCI: Mark all AMD Navi10 and Navi14 GPU ATS as broken (2022-02-23 12:33:32 -0600)
----------------------------------------------------------------
PCI fixes:
- Fix a merge error that broke PCI device enumeration on mvebu platforms,
including Turris Omnia (Armada 385) (Pali Rohár)
- Avoid using ATS on all AMD Navi10 and Navi14 GPUs because some VBIOSes
don't account for "harvested" (disabled) parts of the chip when
initializing caches (Alex Deucher)
----------------------------------------------------------------
Alex Deucher (1):
PCI: Mark all AMD Navi10 and Navi14 GPU ATS as broken
Pali Rohár (1):
PCI: mvebu: Fix device enumeration regression
drivers/pci/controller/pci-mvebu.c | 3 ++-
drivers/pci/quirks.c | 14 +++++++++-----
2 files changed, 11 insertions(+), 6 deletions(-)
next reply other threads:[~2022-02-24 19:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 19:56 Bjorn Helgaas [this message]
2022-02-24 21:40 ` [GIT PULL] PCI fixes for v5.17 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2022-02-11 20:40 Bjorn Helgaas
2022-02-11 21:36 ` pr-tracker-bot
2022-02-04 21:30 Bjorn Helgaas
2022-02-04 23:29 ` pr-tracker-bot
2022-01-29 16:15 Bjorn Helgaas
2022-01-29 17:07 ` pr-tracker-bot
2022-01-20 20:48 Bjorn Helgaas
2022-01-21 7:38 ` 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=20220224195611.GA289605@bhelgaas \
--to=helgaas@kernel.org \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.com \
--cc=guchun.chen@amd.com \
--cc=jpalus@fastmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mail@mcl.gg \
--cc=pali@kernel.org \
--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).