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>,
"Dan Williams" <dan.j.williams@intel.com>,
"Imre Deak" <imre.deak@intel.com>,
"Hans de Goede" <hdegoede@redhat.com>,
"Kalle Valo" <kvalo@kernel.org>,
"Dave Jiang" <dave.jiang@intel.com>,
"Jani Saarinen" <jani.saarinen@intel.com>,
"Leon Romanovsky" <leonro@nvidia.com>
Subject: [GIT PULL] PCI fixes for v6.10
Date: Thu, 6 Jun 2024 13:59:25 -0500 [thread overview]
Message-ID: <20240606185925.GA810710@bhelgaas> (raw)
The following changes since commit 1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0:
Linux 6.10-rc1 (2024-05-26 15:20:12 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git tags/pci-v6.10-fixes-1
for you to fetch changes up to c9d52fb313d3719d69a040f4ca78a3e2e95fba21:
PCI: Revert the cfg_access_lock lockdep mechanism (2024-06-04 12:10:05 -0500)
----------------------------------------------------------------
- Revert lockdep checking on locking that protects device resets from
user-space config accesses; it exposed issues for which fixes are in the
works but are too risky for this cycle (Dan Williams)
----------------------------------------------------------------
Dan Williams (1):
PCI: Revert the cfg_access_lock lockdep mechanism
drivers/pci/access.c | 4 ----
drivers/pci/pci.c | 1 -
drivers/pci/probe.c | 3 ---
include/linux/lockdep.h | 5 -----
include/linux/pci.h | 2 --
5 files changed, 15 deletions(-)
next reply other threads:[~2024-06-06 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 18:59 Bjorn Helgaas [this message]
2024-06-06 21:47 ` [GIT PULL] PCI fixes for v6.10 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2024-07-05 19:05 Bjorn Helgaas
2024-07-05 19:37 ` 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=20240606185925.GA810710@bhelgaas \
--to=helgaas@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=hdegoede@redhat.com \
--cc=imre.deak@intel.com \
--cc=jani.saarinen@intel.com \
--cc=kvalo@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=leonro@nvidia.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox