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>,
"Philipp Stanner" <pstanner@redhat.com>,
"Alex Williamson" <alex.williamson@redhat.com>
Subject: [GIT PULL] PCI fixes for v6.11
Date: Fri, 13 Sep 2024 15:27:17 -0500 [thread overview]
Message-ID: <20240913202717.GA723839@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-4
for you to fetch changes up to fc8c818e756991f5f50b8dfab07f970a18da2556:
PCI: Fix potential deadlock in pcim_intx() (2024-09-12 07:52:50 -0500)
Another fix to a commit merged during the v6.11 merge window.
----------------------------------------------------------------
- Prevent a possible deadlock (reported by lockdep) when a driver
relinquishes a pci_dev, another driver claims it, and one uses
managed pcim_enable_device() and the other doesn't (Philipp Stanner)
----------------------------------------------------------------
Philipp Stanner (1):
PCI: Fix potential deadlock in pcim_intx()
drivers/pci/devres.c | 2 ++
1 file changed, 2 insertions(+)
next reply other threads:[~2024-09-13 20:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 20:27 Bjorn Helgaas [this message]
2024-09-13 21:12 ` [GIT PULL] PCI fixes for v6.11 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2024-09-06 19:37 Bjorn Helgaas
2024-09-07 1:09 ` pr-tracker-bot
2024-08-30 20:57 Bjorn Helgaas
2024-08-31 4:11 ` 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=20240913202717.GA723839@bhelgaas \
--to=helgaas@kernel.org \
--cc=alex.williamson@redhat.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 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.