From: patchwork-bot+bluetooth@kernel.org
To: Kevin Dewald <kevin@simpleble.org>
Cc: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com,
marcel@holtmann.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Bluetooth: hci_event: Clear explicit connect state on LE connection
Date: Fri, 23 Oct 2026 21:00:31 +0000 [thread overview]
Message-ID: <179278923181.1268720.16511882069578397245.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261023191437.87024-1-kevin@simpleble.org>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 23 Oct 2026 12:14:37 -0700 you wrote:
> Since commit 6cd29ec6ae5e ("Bluetooth: hci_sync: Wait for proper events
> when connecting LE"), create_le_conn_complete() only runs once the LE
> Connection Complete event has been handled, and le_conn_complete_evt()
> has already removed the connection parameters from pend_le_conns by
> then. hci_connect_le_scan_cleanup() looks the parameters up in
> pend_le_conns, so after a successful connection it no longer clears
> explicit_connect, nor deletes the parameters that were only created for
> the explicit connect.
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: hci_event: Clear explicit connect state on LE connection
https://git.kernel.org/bluetooth/bluetooth-next/c/083c4a113833
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-10-23 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 19:14 [PATCH v2] Bluetooth: hci_event: Clear explicit connect state on LE connection Kevin Dewald
2026-10-23 21:00 ` patchwork-bot+bluetooth [this message]
2026-10-23 21:09 ` [v2] " bluez.test.bot
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=179278923181.1268720.16511882069578397245.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=kevin@simpleble.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@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 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.