From: patchwork-bot+bluetooth@kernel.org
To: Hans de Goede <johannes.goede@oss.qualcomm.com>
Cc: brgl@kernel.org, marcel@holtmann.org, luiz.dentz@gmail.com,
iabdelka@qti.qualcomm.com, linux-arm-msm@vger.kernel.org,
linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: hci_qca: Do not write to the serial port after it is closed
Date: Thu, 10 Sep 2026 20:50:06 +0000 [thread overview]
Message-ID: <178907340663.2075844.14300677494257499736.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260819125425.192316-1-johannes.goede@oss.qualcomm.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 19 Aug 2026 14:54:25 +0200 you wrote:
> From: Ibrahim Abdelkader <iabdelka@qti.qualcomm.com>
>
> hci_uart_close() closes the serdev port if HCI_QUIRK_NON_PERSISTENT_SETUP
> is set (for example, for the WCN399x family). A failed hci_dev_open_sync()
> following a successful qca_setup() calls hdev->close() but not
> hdev->shutdown(), so the port is closed while power->vregs_on is left true.
> qca_serdev_remove() then passes its power->vregs_on test and calls
> qca_power_off(), which writes to the closed port unconditionally.
>
> [...]
Here is the summary with links:
- Bluetooth: hci_qca: Do not write to the serial port after it is closed
https://git.kernel.org/bluetooth/bluetooth-next/c/6691666bb4b2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-10 20:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 12:54 [PATCH] Bluetooth: hci_qca: Do not write to the serial port after it is closed Hans de Goede
2026-08-19 12:59 ` Hans de Goede
2026-08-19 16:25 ` Luiz Augusto von Dentz
2026-08-19 20:03 ` Hans de Goede
2026-08-19 13:53 ` bluez.test.bot
2026-09-10 18:41 ` bluez.test.bot
2026-09-10 20:50 ` patchwork-bot+bluetooth [this message]
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=178907340663.2075844.14300677494257499736.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=brgl@kernel.org \
--cc=iabdelka@qti.qualcomm.com \
--cc=johannes.goede@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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