All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v4 1/6] shared/bap: fix channel allocation logic in bt_bap_select()
Date: Mon, 17 Nov 2025 19:10:07 +0000	[thread overview]
Message-ID: <176340660753.3444598.13463194800102320570.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <69ef74b5d531804f4f793f42032da508d1497d1b.1763211509.git.pav@iki.fi>

Hello:

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

On Sat, 15 Nov 2025 14:58:28 +0200 you wrote:
> bt_bap_select() does not correctly determine the need for multi-stream
> configurations 6,7,8,9,11(i), as its result depends on whether Audio
> Locations is read before or after the PACs, doesn't work with general
> location bits, etc.
> 
> Fix the procedure to be simpler: create streams for all locations, up to
> a specific number of channels.  By default, limit to max 2 channels per
> direction for compatibility (BAP doesn't have explicit AC with larger
> channel counts.) Also simplify the code.
> 
> [...]

Here is the summary with links:
  - [BlueZ,v4,1/6] shared/bap: fix channel allocation logic in bt_bap_select()
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=f1afca6a097b
  - [BlueZ,v4,2/6] shared/bap: fix packet length comparison to ATT MTU in bap_queue_req()
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=0c56d482fd20
  - [BlueZ,v4,3/6] bap: don't configure endpoints of all codecs at once
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=231372ca5e15
  - [BlueZ,v4,4/6] shared/tester: better debug output on io memcmp failure
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=a1f8862a38a5
  - [BlueZ,v4,5/6] test-bap: make PDU macros parametrizable
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=7858675e6281
  - [BlueZ,v4,6/6] test-bap: add audio configuration selection and streaming tests
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=8a41ac3fde99

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-11-17 19:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-15 12:58 [PATCH BlueZ v4 1/6] shared/bap: fix channel allocation logic in bt_bap_select() Pauli Virtanen
2025-11-15 12:58 ` [PATCH BlueZ v4 2/6] shared/bap: fix packet length comparison to ATT MTU in bap_queue_req() Pauli Virtanen
2025-11-15 12:58 ` [PATCH BlueZ v4 3/6] bap: don't configure endpoints of all codecs at once Pauli Virtanen
2025-11-15 12:58 ` [PATCH BlueZ v4 4/6] shared/tester: better debug output on io memcmp failure Pauli Virtanen
2025-11-15 12:58 ` [PATCH BlueZ v4 5/6] test-bap: make PDU macros parametrizable Pauli Virtanen
2025-11-15 12:58 ` [PATCH BlueZ v4 6/6] test-bap: add audio configuration selection and streaming tests Pauli Virtanen
2025-11-15 14:03 ` [BlueZ,v4,1/6] shared/bap: fix channel allocation logic in bt_bap_select() bluez.test.bot
2025-11-17 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=176340660753.3444598.13463194800102320570.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=pav@iki.fi \
    /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.