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 0/1] Bluetooth: ISO: Pass BIG encryption info through QoS
Date: Wed, 06 Sep 2023 20:30:23 +0000 [thread overview]
Message-ID: <169403222351.1730.3024614854000477917.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230906140103.9183-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 Wed, 6 Sep 2023 17:01:02 +0300 you wrote:
> This patch enables the ISO layer to set the encryption field of
> the broadcast QoS struct, according to a BIGInfo advertising report
> received after PA sync establishment.
>
> This is useful for the broadcast sink scenario: the userspace
> opens a socket and starts listening for a PA sync connection.
> If the PA is associated with an encrypted BIG, the userspace
> needs to be informed.
>
> [...]
Here is the summary with links:
- [1/1] Bluetooth: ISO: Pass BIG encryption info through QoS
https://git.kernel.org/bluetooth/bluetooth-next/c/f2fc183c43e4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-09-06 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 14:01 [PATCH 0/1] Bluetooth: ISO: Pass BIG encryption info through QoS Iulia Tanasescu
2023-09-06 14:01 ` [PATCH 1/1] " Iulia Tanasescu
2023-09-06 14:45 ` bluez.test.bot
2023-09-06 20:30 ` patchwork-bot+bluetooth [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-30 13:01 [PATCH 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=169403222351.1730.3024614854000477917.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).