Linux bluetooth development
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v1 0/7] BAP ASE state handling enhancements
Date: Wed, 04 Nov 2026 19:10:07 +0000	[thread overview]
Message-ID: <179381940730.3059479.12239804796316659769.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261103203011.3904290-1-luiz.dentz@gmail.com>

Hello:

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

On Tue,  3 Nov 2026 15:30:02 -0500 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> 
> The ASCS server deferred the ASE state notifications by 10 ms after the
> ASE Control Point notification, while the client completed requests on
> the CP notification alone, so it could act on a stale ASE state, e.g.
> failing MediaTransport1.Acquire right after Release, whenever the
> notifications were not received together.
> 
> [...]

Here is the summary with links:
  - [BlueZ,v1,1/7] shared/bap: Defer ASE state notifications until idle
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=93c2fcff3f3d
  - [BlueZ,v1,2/7] shared/bap: Wait for ASE state before completing requests
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=0828488099b3
  - [BlueZ,v1,3/7] unit/test-bap: Add tests for cancelling grouped Enable
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=c45e032c9ad3
  - [BlueZ,v1,4/7] unit/test-bap: Add Notify Multiple test
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=43054838bed7
  - [BlueZ,v1,5/7] shared/tester: Add support for alternative PDUs
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=ff30bb4a893f
  - [BlueZ,v1,6/7] unit/test-bap: Expect the ASE state following Releasing
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=1947529d6bb9
  - [BlueZ,v1,7/7] unit/test-bap: Run unicast tests with Notify Multiple
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=121dabd8be93

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-11-04 19:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03 20:30 [PATCH BlueZ v1 0/7] BAP ASE state handling enhancements Luiz Augusto von Dentz
2026-11-03 20:30 ` [PATCH BlueZ v1 1/7] shared/bap: Defer ASE state notifications until idle Luiz Augusto von Dentz
2026-11-03 22:51   ` BAP ASE state handling enhancements bluez.test.bot
2026-11-03 20:30 ` [PATCH BlueZ v1 2/7] shared/bap: Wait for ASE state before completing requests Luiz Augusto von Dentz
2026-11-03 20:30 ` [PATCH BlueZ v1 3/7] unit/test-bap: Add tests for cancelling grouped Enable Luiz Augusto von Dentz
2026-11-03 20:30 ` [PATCH BlueZ v1 4/7] unit/test-bap: Add Notify Multiple test Luiz Augusto von Dentz
2026-11-03 20:30 ` [PATCH BlueZ v1 5/7] shared/tester: Add support for alternative PDUs Luiz Augusto von Dentz
2026-11-03 20:30 ` [PATCH BlueZ v1 6/7] unit/test-bap: Expect the ASE state following Releasing Luiz Augusto von Dentz
2026-11-03 20:30 ` [PATCH BlueZ v1 7/7] unit/test-bap: Run unicast tests with Notify Multiple Luiz Augusto von Dentz
2026-11-04 19:10 ` 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=179381940730.3059479.12239804796316659769.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox