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
Subject: Re: [PATCH BlueZ v3 0/1] Split bt_iso_qos into dedicated structures
Date: Fri, 31 Mar 2023 22:10:18 +0000	[thread overview]
Message-ID: <168030061881.9780.2905721652873874499.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230331153927.35411-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 Fri, 31 Mar 2023 18:39:26 +0300 you wrote:
> This patch adds support for additional ISO broadcast QoS parameters,
> that the user can set before performing broadcast procedures
> using an ISO socket.
> 
> This patch splits the "bt_iso_qos" structure into dedicated
> unicast and broadcast structures, so that ISO sockets
> can be configured with dedicated QoS options depending
> on the type of ISO procedures to run.
> 
> [...]

Here is the summary with links:
  - [BlueZ,v3,1/1] Split bt_iso_qos into dedicated structures
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=c4d9b99db5a6

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-03-31 22:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31 15:39 [PATCH BlueZ v3 0/1] Split bt_iso_qos into dedicated structures Iulia Tanasescu
2023-03-31 15:39 ` [PATCH BlueZ v3 1/1] " Iulia Tanasescu
2023-03-31 17:10   ` bluez.test.bot
2023-03-31 22: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=168030061881.9780.2905721652873874499.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=iulia.tanasescu@nxp.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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.