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 0/1] Bluetooth: ISO: Match QoS adv handle with BIG handle
Date: Tue, 03 Oct 2023 17:10:27 +0000	[thread overview]
Message-ID: <169635302745.22624.9791942110142970744.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231003143739.2925-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 Tue,  3 Oct 2023 17:37:38 +0300 you wrote:
> Currently, if the user wants to bind multiple broadcast sockets to the
> same BIG handle, the BIG and BIS fields of the QoS structs must be set
> and identical for all sockets.
> 
> It means that the user must remember both the BIG handle and the
> associated advertising handle that the BIG will be opened for.
> This information is redundant, since one BIG handle may only be
> associated with an unique adv handle.
> 
> [...]

Here is the summary with links:
  - [1/1] Bluetooth: ISO: Match QoS adv handle with BIG handle
    https://git.kernel.org/bluetooth/bluetooth-next/c/cffdc28aa2e2

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 17:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-03 14:37 [PATCH 0/1] Bluetooth: ISO: Match QoS adv handle with BIG handle Iulia Tanasescu
2023-10-03 14:37 ` [PATCH 1/1] " Iulia Tanasescu
2023-10-03 15:42   ` bluez.test.bot
2023-10-03 17:10 ` patchwork-bot+bluetooth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-29 15:37 [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=169635302745.22624.9791942110142970744.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.