All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Nguyen Ngoc Thang <ngocthang2710.1999@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
	syzbot+217e3f1283cafe80586e@syzkaller.appspotmail.com
Subject: Re: [PATCH] Bluetooth: hci_sync: don't drain cmd_sync backlog on unregister
Date: Mon, 28 Sep 2026 15:40:22 +0000	[thread overview]
Message-ID: <179061002265.4169639.8219573133250587416.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260927151802.13619-1-ngocthang2710.1999@gmail.com>

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Sun, 27 Sep 2026 22:18:02 +0700 you wrote:
> hci_unregister_dev() disables cmd_work and cmd_timer, then calls
> hci_cmd_sync_clear(), whose cancel_work_sync() waits for
> hci_cmd_sync_work() to return. That worker dequeues and runs every
> entry on cmd_sync_work_list. With cmd_work disabled nothing reaches
> the controller, so each queued HCI command waits the full
> HCI_CMD_TIMEOUT (2s).
> 
> [...]

Here is the summary with links:
  - Bluetooth: hci_sync: don't drain cmd_sync backlog on unregister
    https://git.kernel.org/bluetooth/bluetooth-next/c/b1f24c1ab523

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-09-28 15:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-27 15:18 [PATCH] Bluetooth: hci_sync: don't drain cmd_sync backlog on unregister Nguyen Ngoc Thang
2026-09-27 23:26 ` bluez.test.bot
2026-09-28 15:40 ` 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=179061002265.4169639.8219573133250587416.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=ngocthang2710.1999@gmail.com \
    --cc=syzbot+217e3f1283cafe80586e@syzkaller.appspotmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.