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
Subject: Re: [PATCH v3 0/1] Bluetooth: ISO: Use defer setup to separate PA sync and BIG sync
Date: Thu, 17 Aug 2023 19:50:21 +0000	[thread overview]
Message-ID: <169230182199.7718.11583848723742447156.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230817064427.3647-1-iulia.tanasescu@nxp.com>

Hello:

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

On Thu, 17 Aug 2023 09:44:26 +0300 you wrote:
> Some scenarios require a Broadcast Sink to complete the PA sync and
> BIG sync procedures separately.
> 
> For example, a Broadcast Sink might synchronize to the periodic
> advertising transmitted by a Broadcast Source and it might detect
> that the BIG is encrypted, by looking at the BIGInfo advertising
> reports. If the Broadcast Sink doesn't know which Broadcast Code
> to pass as parameter to the BIG Create Sync command, it might learn
> it from a BASS Client through the Set Broadcast Code operation.
> Only then will it be able to successfully sync to the BIG.
> 
> [...]

Here is the summary with links:
  - [v3,1/1] Bluetooth: ISO: Use defer setup to separate PA sync and BIG sync
    https://git.kernel.org/bluetooth/bluetooth-next/c/f0835e7404b7

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-08-17 19:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-17  6:44 [PATCH v3 0/1] Bluetooth: ISO: Use defer setup to separate PA sync and BIG sync Iulia Tanasescu
2023-08-17  6:44 ` [PATCH v3 1/1] " Iulia Tanasescu
2023-08-17  7:35   ` bluez.test.bot
2023-08-17 20:26   ` [PATCH v3 1/1] " Pauli Virtanen
2023-08-17 21:39     ` Luiz Augusto von Dentz
2023-08-18 11:10       ` Iulia Tanasescu
2023-08-17 19:50 ` 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=169230182199.7718.11583848723742447156.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=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.