From: patchwork-bot+bluetooth@kernel.org
To: Cen Zhang <zzzccc427@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org, baijiaju1990@gmail.com
Subject: Re: [PATCH] Bluetooth: MGMT: Fix adv monitor add failure cleanup
Date: Fri, 26 Jun 2026 11:16:47 +0000 [thread overview]
Message-ID: <178247260729.3816447.3243373434534178478.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260623161328.2177234-1-zzzccc427@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 24 Jun 2026 00:13:28 +0800 you wrote:
> hci_add_adv_monitor() publishes a new adv_monitor in
> hdev->adv_monitors_idr before the powered MSFT setup step. The MSFT
> offload add path can then fail either locally before the controller add
> command completes, or in the MSFT add callback. In the current queued
> management add flow, hci_cmd_sync_work() still invokes
> mgmt_add_adv_patterns_monitor_complete() with the original pending command
> after msft_add_monitor_pattern() returns.
>
> [...]
Here is the summary with links:
- Bluetooth: MGMT: Fix adv monitor add failure cleanup
https://git.kernel.org/bluetooth/bluetooth-next/c/7083dd331667
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-06-26 11:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 16:13 [PATCH] Bluetooth: MGMT: Fix adv monitor add failure cleanup Cen Zhang
2026-06-23 18:05 ` bluez.test.bot
2026-06-26 11:16 ` 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=178247260729.3816447.3243373434534178478.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=baijiaju1990@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=zzzccc427@gmail.com \
/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