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>,
"Bartosz Golaszewski" <bartosz.golaszewski@linaro.org>,
"Johan Hovold" <johan@kernel.org>,
"Konrad Dybcio" <konradybcio@kernel.org>
Subject: [GIT PULL] PCI fixes for v6.12
Date: Fri, 25 Oct 2024 12:31:25 -0500 [thread overview]
Message-ID: <20241025173125.GA1026995@bhelgaas> (raw)
The following changes since commit 9852d85ec9d492ebef56dc5f229416c925758edc:
Linux 6.12-rc1 (2024-09-29 15:06:19 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git tags/pci-v6.12-fixes-1
for you to fetch changes up to ad783b9f8e78572fff3b04b6caee7bea3821eea8:
PCI/pwrctl: Abandon QCom WCN probe on pre-pwrseq device-trees (2024-10-23 13:34:41 -0500)
----------------------------------------------------------------
- Hold the rescan lock while adding devices to avoid race with concurrent
pwrctl rescan that can lead to a crash (Bartosz Golaszewski)
- Avoid binding pwrctl driver to QCom WCN wifi if the DT lacks the
necessary PMU regulator descriptions (Bartosz Golaszewski)
----------------------------------------------------------------
Bartosz Golaszewski (2):
PCI: Hold rescan lock while adding devices during host probe
PCI/pwrctl: Abandon QCom WCN probe on pre-pwrseq device-trees
drivers/pci/probe.c | 2 ++
drivers/pci/pwrctl/pci-pwrctl-pwrseq.c | 55 ++++++++++++++++++++++++++++++----
2 files changed, 52 insertions(+), 5 deletions(-)
next reply other threads:[~2024-10-25 17:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 17:31 Bjorn Helgaas [this message]
2024-10-25 18:10 ` pr-tracker-bot
2024-11-01 20:51 Bjorn Helgaas
2024-11-02 1: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=20241025173125.GA1026995@bhelgaas \
--to=helgaas@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=johan@kernel.org \
--cc=konradybcio@kernel.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=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
all inboxes | Powered by JetHome®