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>,
"Brian Norris" <briannorris@chromium.org>,
"Saurabh Sengar" <ssengar@linux.microsoft.com>
Subject: [GIT PULL] PCI fixes for v6.13
Date: Sat, 30 Nov 2024 18:14:44 -0600 [thread overview]
Message-ID: <20241201001444.GA2843588@bhelgaas> (raw)
The following changes since commit 10099266dec8275a6899e6a27dcdfebbcc726cc7:
Merge branch 'pci/typos' (2024-11-25 13:41:00 -0600)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git tags/pci-v6.13-fixes-1
for you to fetch changes up to 5c8418cf4025388bedd4d65ada993f7d3786cc3a:
PCI/pwrctrl: Unregister platform device only if one actually exists (2024-11-30 11:41:25 -0600)
----------------------------------------------------------------
- When removing a PCI device, only look up and remove a platform device
if there is an associated device node for which there could be a platform
device, to fix a merge window regression (Brian Norris)
----------------------------------------------------------------
Brian Norris (1):
PCI/pwrctrl: Unregister platform device only if one actually exists
drivers/pci/remove.c | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
next reply other threads:[~2024-12-01 0:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-01 0:14 Bjorn Helgaas [this message]
2024-12-01 2:41 ` [GIT PULL] PCI fixes for v6.13 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2024-12-21 13:12 Krzysztof Wilczyński
2024-12-21 18:56 ` pr-tracker-bot
2025-01-14 18:56 Bjorn Helgaas
2025-01-14 19:55 ` 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=20241201001444.GA2843588@bhelgaas \
--to=helgaas@kernel.org \
--cc=briannorris@chromium.org \
--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=ssengar@linux.microsoft.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