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, andrei.istodorescu@nxp.com,
	luiz.dentz@gmail.com
Subject: Re: [PATCH BlueZ 0/2] shared/bap: Fix BASE parsing
Date: Fri, 17 Jan 2025 18:10:33 +0000	[thread overview]
Message-ID: <173713743350.2213962.13510645298591326713.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250117140632.120501-1-iulia.tanasescu@nxp.com>

Hello:

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

On Fri, 17 Jan 2025 16:06:30 +0200 you wrote:
> This patch adds some fixes for the BASE parsing logic in BAP:
> 
> The first commit fixes the getsockopt call for BT_ISO_BASE, to
> make sure that the correct BASE length is read from the kernel.
> 
> The second commit adds a missing case in the BASE parsing logic
> for Broadcast Sinks: the BASE structure might contain level 3
> (BIS specific) configuration LTV types that are not present at
> level 2 (subgroup level). These values should also be appended
> to the final BIS configuration.
> 
> [...]

Here is the summary with links:
  - [BlueZ,1/2] btio: Set correct length for getsockopt
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=07e8e726758f
  - [BlueZ,2/2] shared/bap: Append extra L3 LTVs to BIS config
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=1479c86ec116

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



      parent reply	other threads:[~2025-01-17 18:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-17 14:06 [PATCH BlueZ 0/2] shared/bap: Fix BASE parsing Iulia Tanasescu
2025-01-17 14:06 ` [PATCH BlueZ 1/2] btio: Set correct length for getsockopt Iulia Tanasescu
2025-01-17 15:06   ` shared/bap: Fix BASE parsing bluez.test.bot
2025-01-17 14:06 ` [PATCH BlueZ 2/2] shared/bap: Append extra L3 LTVs to BIS config Iulia Tanasescu
2025-01-17 18:10 ` 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=173713743350.2213962.13510645298591326713.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 \
    /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.