All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Siwei Zhang <oss@fourdim.xyz>
Cc: luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v3] Bluetooth: L2CAP: Reject signalling responses in invalid states
Date: Wed, 14 Oct 2026 17:20:11 +0000	[thread overview]
Message-ID: <179199841101.2868755.9541484050072201773.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261007144717.3832330-1-oss@fourdim.xyz>

Hello:

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

On Wed,  7 Oct 2026 10:47:10 -0400 you wrote:
> A peer can send configuration messages while an
> incoming channel is in BT_CONNECT2, before the
> security or deferred accept gate has completed. A
> configuration response can then promote the channel
> to BT_CONNECTED. Configuration responses can also
> act on channels that are closing, and a late connection
> response can move a disconnecting channel back to
> BT_CONFIG.
> 
> [...]

Here is the summary with links:
  - [v3] Bluetooth: L2CAP: Reject signalling responses in invalid states
    https://git.kernel.org/bluetooth/bluetooth-next/c/0ff5a6d955bd

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-10-14 17:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-07 14:47 [PATCH v3] Bluetooth: L2CAP: Reject signalling responses in invalid states Siwei Zhang
2026-10-07 15:49 ` Luiz Augusto von Dentz
2026-10-07 16:24   ` Siwei Zhang
2026-10-14 17:20 ` 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=179199841101.2868755.9541484050072201773.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=oss@fourdim.xyz \
    /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.