From: patchwork-bot+bluetooth@kernel.org
To: Chengyi Zhao <chengyi.zhao@qq.com>
Cc: linux-bluetooth@vger.kernel.org, luiz.von.dentz@intel.com,
marcel@holtmann.org, zhaochengyi@uniontech.com
Subject: Re: [PATCH BlueZ] policy: Connect profiles for bonded inbound ACL connections
Date: Mon, 20 Jul 2026 19:40:07 +0000 [thread overview]
Message-ID: <178457640714.4136385.3590514668103148608.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <tencent_7E6A07CE6162892EDEFA29E082F2D2A8AE05@qq.com>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 16 Jul 2026 18:55:03 +0800 you wrote:
> From: Chengyi Zhao <zhaochengyi@uniontech.com>
>
> When a bonded device initiates an inbound ACL connection (e.g. after
> resume, the remote wins the page race), BlueZ accepts the ACL link
> but does not establish AVDTP/AVCTP profiles. The remote's subsequent
> L2CAP connect for PSM 25 fails with "security block" because the link
> is not yet encrypted, and the kernel does not retry. The ACL link
> stays up with no audio.
>
> [...]
Here is the summary with links:
- [BlueZ] policy: Connect profiles for bonded inbound ACL connections
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=f3f03d728542
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-07-20 19:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 10:55 [PATCH BlueZ] policy: Connect profiles for bonded inbound ACL connections Chengyi Zhao
2026-07-16 12:37 ` [BlueZ] " bluez.test.bot
2026-07-20 19: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=178457640714.4136385.3590514668103148608.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=chengyi.zhao@qq.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=zhaochengyi@uniontech.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.