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>,
"Jim Quinlan" <james.quinlan@broadcom.com>,
"Lukas Wunner" <lukas@wunner.de>
Subject: [GIT PULL] PCI fixes for v6.16
Date: Thu, 24 Jul 2025 17:10:09 -0500 [thread overview]
Message-ID: <20250724221009.GA3059501@bhelgaas> (raw)
The following changes since commit 19272b37aa4f83ca52bdf9c16d5d81bdd1354494:
Linux 6.16-rc1 (2025-06-08 13:44:43 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git tags/pci-v6.16-fixes-4
for you to fetch changes up to 8c493cc91f3a1102ad2f8c75ae0cf80f0a057488:
PCI/pwrctrl: Create pwrctrl devices only when CONFIG_PCI_PWRCTRL is enabled (2025-07-22 13:36:04 -0500)
----------------------------------------------------------------
- Create pwrctrl devices only when we need them, i.e., when
CONFIG_PCI_PWRCTRL is enabled; this allows brcmstb to work around a
pwrctrl regression by disabling CONFIG_PCI_PWRCTRL (Manivannan
Sadhasivam)
----------------------------------------------------------------
Manivannan Sadhasivam (1):
PCI/pwrctrl: Create pwrctrl devices only when CONFIG_PCI_PWRCTRL is enabled
drivers/pci/probe.c | 7 +++++++
1 file changed, 7 insertions(+)
next reply other threads:[~2025-07-24 22:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 22:10 Bjorn Helgaas [this message]
2025-07-24 22:42 ` [GIT PULL] PCI fixes for v6.16 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2025-07-11 20:28 Bjorn Helgaas
2025-07-12 0:29 ` pr-tracker-bot
2025-06-27 20:27 Bjorn Helgaas
2025-06-28 3:28 ` pr-tracker-bot
2025-06-20 19:49 Bjorn Helgaas
2025-06-21 15:47 ` 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=20250724221009.GA3059501@bhelgaas \
--to=helgaas@kernel.org \
--cc=james.quinlan@broadcom.com \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=lukas@wunner.de \
--cc=mani@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