From: patchwork-bot+bluetooth@kernel.org
To: Michael McAllister <me@michaelmcallister.org>
Cc: markus.probst@posteo.de, luiz.dentz@gmail.com,
marcel@holtmann.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Bluetooth: hci_mrvl: Leave the serdev port lifetime to hci_serdev
Date: Tue, 17 Nov 2026 18:50:15 +0000 [thread overview]
Message-ID: <179494141527.761488.11110930230675526211.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <179484691454.54083.14464729860702732145.marvell-serdev-v2@michaelmcallister.org>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 16 Nov 2026 16:35:14 +0000 you wrote:
> hci_uart_register_device_priv() opens the port before calling mrvl_open(),
> so Marvell opens it twice. Likewise, mrvl_close() closes it before the
> transport closes it again during unregister or registration error cleanup.
>
> Remove the extra calls and let hci_serdev own the port lifetime. This also
> avoids failing probe when serdev rejects a second open with -EALREADY.
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: hci_mrvl: Leave the serdev port lifetime to hci_serdev
https://git.kernel.org/bluetooth/bluetooth-next/c/c9eb955c4fe2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-11-17 18:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 22:34 [PATCH 0/4] Bluetooth: qca: Fix WCN3950 power-off Michael McAllister
2026-10-28 22:34 ` [PATCH 2/4] Bluetooth: hci_serdev: Track whether the serial port is open Michael McAllister
2026-11-12 18:56 ` Markus Probst
2026-11-14 16:15 ` [PATCH 0/1] Bluetooth: hci_mrvl: Fix duplicate serdev open/close Michael McAllister
2026-11-14 16:15 ` [PATCH 1/1] Bluetooth: hci_mrvl: Leave the serdev port lifetime to hci_serdev Michael McAllister
2026-11-16 16:35 ` [PATCH v2] " Michael McAllister
2026-11-16 16:41 ` Loic Poulain
2026-11-17 18:50 ` patchwork-bot+bluetooth [this message]
2026-11-17 12:36 ` [PATCH 1/1] " Sascha Hauer
2026-11-14 17:06 ` [PATCH 0/1] Bluetooth: hci_mrvl: Fix duplicate serdev open/close Markus Probst
2026-11-17 18:50 ` patchwork-bot+bluetooth
2026-10-28 22:34 ` [PATCH 1/4] Bluetooth: qca: Restore flow control after a failed power pulse Michael McAllister
2026-10-28 22:34 ` [PATCH 3/4] Bluetooth: qca: Power off after unregistering the HCI device Michael McAllister
2026-10-28 22:34 ` [PATCH 4/4] Bluetooth: qca: Power off WCN3950 Michael McAllister
2026-11-14 18:39 ` [PATCH v2 0/4] " Michael McAllister
2026-11-14 18:39 ` [PATCH v2 2/4] Bluetooth: qca: Power off after unregistering the HCI device Michael McAllister
2026-11-16 8:38 ` Zhao Li
2026-11-14 18:39 ` [PATCH v2 3/4] Bluetooth: qca: Handle failed power-pulse writes Michael McAllister
2026-11-14 18:39 ` [PATCH v2 1/4] Bluetooth: hci_serdev: Track whether the serial port is open Michael McAllister
2026-11-14 18:39 ` [PATCH v2 4/4] Bluetooth: qca: Power off WCN3950 Michael McAllister
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=179494141527.761488.11110930230675526211.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=markus.probst@posteo.de \
--cc=me@michaelmcallister.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®