From: patchwork-bot+bluetooth@kernel.org
To: Michael Grzeschik <m.grzeschik@pengutronix.de>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH] net: bluetooth: hci_sync: fix hci_le_create_conn_sync
Date: Thu, 05 Mar 2026 15:50:09 +0000 [thread overview]
Message-ID: <177272580905.3180764.3868114143946058226.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260305-bluetooth-fixes-v1-1-43effb810fba@pengutronix.de>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 05 Mar 2026 14:50:52 +0100 you wrote:
> While introducing hci_le_create_conn_sync the functionality
> of hci_connect_le was ported to hci_le_create_conn_sync including
> the disable of the scan before starting the connection.
>
> When this code was run non synchronously the immediate call that was
> setting the flag HCI_LE_SCAN_INTERRUPTED had an impact. Since the
> completion handler for the LE_SCAN_DISABLE was not immediately called.
> In the completion handler of the LE_SCAN_DISABLE event, this flag is
> checked to set the state of the hdev to DISCOVERY_STOPPED.
>
> [...]
Here is the summary with links:
- net: bluetooth: hci_sync: fix hci_le_create_conn_sync
https://git.kernel.org/bluetooth/bluetooth-next/c/ae93951e4081
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-03-05 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 13:50 [PATCH] net: bluetooth: hci_sync: fix hci_le_create_conn_sync Michael Grzeschik
2026-03-05 14:20 ` Luiz Augusto von Dentz
2026-03-05 14:21 ` bluez.test.bot
2026-03-05 15: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=177272580905.3180764.3868114143946058226.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=johan.hedberg@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=m.grzeschik@pengutronix.de \
--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