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/6] Add true wireless BAP broadcast tests
Date: Tue, 22 Sep 2026 15:00:16 +0000	[thread overview]
Message-ID: <179008921688.4126096.7132229331196034449.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260921210123.3690449-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 Mon, 21 Sep 2026 17:01:17 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> 
> This adds functional tests for broadcast setups where the left and the
> right side are separate devices, as in a pair of earbuds, which so far
> were only covered with a single sink taking both channels.
> 
> The source broadcasts one BIS per channel, and each side registers a
> single location, so each of them only gets a transport for the BIS
> carrying its own channel: the sides are told apart by the BIS index of
> the transport path.
> 
> [...]

Here is the summary with links:
  - [BlueZ,v1,1/6] doc: describe the true wireless broadcast test cases
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=086a30e3cf47
  - [BlueZ,v1,2/6] doc: describe the true wireless broadcast assistant test case
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=4c8102eecc20
  - [BlueZ,v1,3/6] test: functional: add the true wireless broadcast tests
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=547afc7ef35c
  - [BlueZ,v1,4/6] bass: keep the push target per MediaAssistant object
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=bb59c19e299f
  - [BlueZ,v1,5/6] client: connect a device that is already paired
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=e691da62c62f
  - [BlueZ,v1,6/6] test: functional: add the true wireless broadcast assistant test
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=98d6d1350a6a

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-09-22 15:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-21 21:01 [PATCH BlueZ v1 0/6] Add true wireless BAP broadcast tests Luiz Augusto von Dentz
2026-09-21 21:01 ` [PATCH BlueZ v1 1/6] doc: describe the true wireless broadcast test cases Luiz Augusto von Dentz
2026-09-21 23:47   ` Add true wireless BAP broadcast tests bluez.test.bot
2026-09-21 21:01 ` [PATCH BlueZ v1 2/6] doc: describe the true wireless broadcast assistant test case Luiz Augusto von Dentz
2026-09-21 21:01 ` [PATCH BlueZ v1 3/6] test: functional: add the true wireless broadcast tests Luiz Augusto von Dentz
2026-09-21 21:01 ` [PATCH BlueZ v1 4/6] bass: keep the push target per MediaAssistant object Luiz Augusto von Dentz
2026-09-21 21:01 ` [PATCH BlueZ v1 5/6] client: connect a device that is already paired Luiz Augusto von Dentz
2026-09-21 21:01 ` [PATCH BlueZ v1 6/6] test: functional: add the true wireless broadcast assistant test Luiz Augusto von Dentz
2026-09-22 15:00 ` 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=179008921688.4126096.7132229331196034449.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