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>,
"Blazej Kucman" <blazej.kucman@intel.com>,
"Philipp Stanner" <pstanner@redhat.com>,
"Damien Le Moal" <dlemoal@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Subject: [GIT PULL] PCI fixes for v6.11
Date: Thu, 1 Aug 2024 13:15:14 -0500 [thread overview]
Message-ID: <20240801181514.GA112131@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 tags/pci-v6.11-fixes-1
for you to fetch changes up to 5560a612c20d3daacbf5da7913deefa5c31742f4:
PCI: pciehp: Retain Power Indicator bits for userspace indicators (2024-08-01 12:58:03 -0500)
N.B. These have been in linux-next since July 26; I updated the commit logs
today to add a Tested-by and an error message.
----------------------------------------------------------------
- Fix a pci_intx() regression that caused driver reload to fail with
"Resources present before probing" (Philipp Stanner)
- Fix a pciehp regression that clobbered the upper bits of RAID status LEDs
on NVMe devices behind an Intel VMD (Blazej Kucman)
----------------------------------------------------------------
Blazej Kucman (1):
PCI: pciehp: Retain Power Indicator bits for userspace indicators
Philipp Stanner (1):
PCI: Fix devres regression in pci_intx()
drivers/pci/hotplug/pciehp_hpc.c | 4 +++-
drivers/pci/pci.c | 15 ++++++++-------
2 files changed, 11 insertions(+), 8 deletions(-)
next reply other threads:[~2024-08-01 18:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 18:15 Bjorn Helgaas [this message]
2024-08-01 18:36 ` [GIT PULL] PCI fixes for v6.11 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2024-08-30 20:57 Bjorn Helgaas
2024-08-31 4:11 ` pr-tracker-bot
2024-09-06 19:37 Bjorn Helgaas
2024-09-07 1:09 ` pr-tracker-bot
2024-09-13 20:27 Bjorn Helgaas
2024-09-13 21:12 ` 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=20240801181514.GA112131@bhelgaas \
--to=helgaas@kernel.org \
--cc=blazej.kucman@intel.com \
--cc=dlemoal@kernel.org \
--cc=ilpo.jarvinen@linux.intel.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=pstanner@redhat.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