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>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"David Woodhouse" <dwmw2@infradead.org>,
"Baruch Siach" <baruch@tkos.co.il>,
"Alex Williamson" <alex@shazbot.org>,
"Niklas Cassel" <cassel@kernel.org>,
"Frank Li" <Frank.Li@nxp.com>,
"Shin'ichiro Kawasaki" <shinichiro.kawasaki@wdc.com>,
"Koichiro Den" <den@valinux.co.jp>,
"Shawn Guo" <shawnguo@kernel.org>,
kvm@vger.kernel.org
Subject: [GIT PULL] PCI fixes for v7.0
Date: Fri, 27 Feb 2026 14:08:59 -0600 [thread overview]
Message-ID: <20260227200859.GA3913790@bhelgaas> (raw)
The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git tags/pci-v7.0-fixes-2
for you to fetch changes up to 39195990e4c093c9eecf88f29811c6de29265214:
PCI: Correct PCI_CAP_EXP_ENDPOINT_SIZEOF_V2 value (2026-02-27 10:24:25 -0600)
The last two commits fix issues that are quite old, but I think they're
worth including in v7.0.
----------------------------------------------------------------
- Update MAINTAINERS email address (Shawn Guo)
- Refresh cached Endpoint driver MSI Message Address to fix a v7.0
regression when kernel changes the address after firmware has configured
it (Niklas Cassel)
- Flush Endpoint MSI-X writes so they complete before the outbound ATU
entry is unmapped (Niklas Cassel)
- Correct the PCI_CAP_EXP_ENDPOINT_SIZEOF_V2 value, which broke VMM use of
PCI capabilities (Bjorn Helgaas)
----------------------------------------------------------------
Bjorn Helgaas (1):
PCI: Correct PCI_CAP_EXP_ENDPOINT_SIZEOF_V2 value
Niklas Cassel (2):
PCI: dwc: ep: Refresh MSI Message Address cache on change
PCI: dwc: ep: Flush MSI-X write before unmapping its ATU entry
Shawn Guo (1):
MAINTAINERS: Update Shawn Guo's address for HiSilicon PCIe controller driver
MAINTAINERS | 2 +-
drivers/pci/controller/dwc/pcie-designware-ep.c | 25 ++++++++++++++++---------
include/uapi/linux/pci_regs.h | 2 +-
3 files changed, 18 insertions(+), 11 deletions(-)
next reply other threads:[~2026-02-27 20:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 20:08 Bjorn Helgaas [this message]
2026-02-27 21:46 ` [GIT PULL] PCI fixes for v7.0 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2026-03-27 14:36 Bjorn Helgaas
2026-03-27 20:39 ` pr-tracker-bot
2026-03-19 21:07 Bjorn Helgaas
2026-03-19 23:30 ` pr-tracker-bot
2026-03-06 21:23 Bjorn Helgaas
2026-03-06 21:56 ` pr-tracker-bot
2026-02-20 19:07 Bjorn Helgaas
2026-02-21 1:20 ` 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=20260227200859.GA3913790@bhelgaas \
--to=helgaas@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=alex@shazbot.org \
--cc=baruch@tkos.co.il \
--cc=cassel@kernel.org \
--cc=den@valinux.co.jp \
--cc=dwmw2@infradead.org \
--cc=kvm@vger.kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mani@kernel.org \
--cc=shawnguo@kernel.org \
--cc=shinichiro.kawasaki@wdc.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