From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2 1/2] Bluetooth: SMP: If an unallowed command is received consider it a failure
Date: Thu, 10 Jul 2025 17:32:47 +0000 [thread overview]
Message-ID: <175216876774.1607762.5527949828152506084.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250702162352.1374119-1-luiz.dentz@gmail.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 2 Jul 2025 12:23:51 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> If a command is received while a bonding is ongoing consider it a
> pairing failure so the session is cleanup properly and the device is
> disconnected immediately instead of continuing with other commands that
> may result in the session to get stuck without ever completing such as
> the case bellow:
>
> [...]
Here is the summary with links:
- [v2,1/2] Bluetooth: SMP: If an unallowed command is received consider it a failure
https://git.kernel.org/bluetooth/bluetooth-next/c/11040353f444
- [v2,2/2] Bluetooth: SMP: Fix using HCI_ERROR_REMOTE_USER_TERM on timeout
https://git.kernel.org/bluetooth/bluetooth-next/c/3f412d11ddf5
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:[~2025-07-10 17:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 16:23 [PATCH v2 1/2] Bluetooth: SMP: If an unallowed command is received consider it a failure Luiz Augusto von Dentz
2025-07-02 16:23 ` [PATCH v2 2/2] Bluetooth: SMP: Fix using HCI_ERROR_REMOTE_USER_TERM on timeout Luiz Augusto von Dentz
2025-07-02 17:11 ` [v2,1/2] Bluetooth: SMP: If an unallowed command is received consider it a failure bluez.test.bot
2025-07-10 17:32 ` 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=175216876774.1607762.5527949828152506084.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@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 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.