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" <manivannan.sadhasivam@linaro.org>,
"Frank Li" <Frank.Li@nxp.com>
Subject: [GIT PULL] PCI fixes for v6.11
Date: Fri, 30 Aug 2024 15:57:33 -0500 [thread overview]
Message-ID: <20240830205733.GA126293@bhelgaas> (raw)
The following changes since commit 8400291e289ee6b2bf9779ff1c83a291501f017b:
Linux 6.11-rc1 (2024-07-28 14:19:55 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git pci-v6.11-fixes-2
for you to fetch changes up to 150b572a7c1df30f5d32d87ad96675200cca7b80:
MAINTAINERS: PCI: Add NXP PCI controller mailing list imx@lists.linux.dev (2024-08-30 13:07:21 -0500)
----------------------------------------------------------------
- Add Manivannan Sadhasivam as PCI native host bridge and endpoint driver
reviewer (Manivannan Sadhasivam)
- Disable MHI RAM data parity error interrupt for qcom SA8775P SoC to work
around hardware erratum that causes a constant stream of interrupts
(Manivannan Sadhasivam)
- Don't try to fall back to qcom Operating Performance Points (OPP) support
unless the platform actually supports OPP (Manivannan Sadhasivam)
- Add imx@lists.linux.dev mailing list to MAINTAINERS for NXP layerscape
and imx6 PCI controller drivers (Frank Li)
----------------------------------------------------------------
Frank Li (1):
MAINTAINERS: PCI: Add NXP PCI controller mailing list imx@lists.linux.dev
Manivannan Sadhasivam (3):
MAINTAINERS: Add Manivannan Sadhasivam as Reviewer for PCI native host bridge and endpoint drivers
PCI: qcom-ep: Disable MHI RAM data parity error interrupt for SA8775P SoC
PCI: qcom: Use OPP only if the platform supports it
MAINTAINERS | 3 +++
drivers/pci/controller/dwc/pcie-qcom-ep.c | 13 +++++++++++++
drivers/pci/controller/dwc/pcie-qcom.c | 7 +++++--
3 files changed, 21 insertions(+), 2 deletions(-)
next reply other threads:[~2024-08-30 20:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 20:57 Bjorn Helgaas [this message]
2024-08-31 4:11 ` [GIT PULL] PCI fixes for v6.11 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2024-09-13 20:27 Bjorn Helgaas
2024-09-13 21:12 ` pr-tracker-bot
2024-09-06 19:37 Bjorn Helgaas
2024-09-07 1:09 ` pr-tracker-bot
2024-08-01 18:15 Bjorn Helgaas
2024-08-01 18:36 ` 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=20240830205733.GA126293@bhelgaas \
--to=helgaas@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=manivannan.sadhasivam@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.