All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Iulia Tanasescu <iulia.tanasescu@nxp.com>
Cc: linux-bluetooth@vger.kernel.org, claudia.rosu@nxp.com,
	mihai-octavian.urzica@nxp.com, silviu.barbulescu@nxp.com,
	vlad.pruteanu@nxp.com, andrei.istodorescu@nxp.com,
	luiz.dentz@gmail.com
Subject: Re: [PATCH BlueZ 0/1] iso-tester: Test bcast receiver with PA sync, no BIS
Date: Tue, 03 Oct 2023 23:20:29 +0000	[thread overview]
Message-ID: <169637522925.21629.4960466643593190621.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231003145754.3667-1-iulia.tanasescu@nxp.com>

Hello:

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

On Tue,  3 Oct 2023 17:57:53 +0300 you wrote:
> Some BASS test scenarios require the BASS Server to only sync to the
> PA transmitted by a source, and not any BIS.
> 
> This patch implements a test to exercise this scenario, where a broadcast
> receiver is able to successfully perform PA sync, without listening for
> any BIS.
> 
> [...]

Here is the summary with links:
  - [BlueZ,1/1] iso-tester: Test bcast receiver with PA sync, no BIS
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=d9445f6d0f08

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



  parent reply	other threads:[~2023-10-03 23:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-03 14:57 [PATCH BlueZ 0/1] iso-tester: Test bcast receiver with PA sync, no BIS Iulia Tanasescu
2023-10-03 14:57 ` [PATCH BlueZ 1/1] " Iulia Tanasescu
2023-10-03 16:25   ` bluez.test.bot
2023-10-03 23:20 ` patchwork-bot+bluetooth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-28 14:28 [PATCH BlueZ 0/1] " Iulia Tanasescu

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=169637522925.21629.4960466643593190621.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=andrei.istodorescu@nxp.com \
    --cc=claudia.rosu@nxp.com \
    --cc=iulia.tanasescu@nxp.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=mihai-octavian.urzica@nxp.com \
    --cc=silviu.barbulescu@nxp.com \
    --cc=vlad.pruteanu@nxp.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.