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 BlueZ v3 0/2] shared/bass: Introduce Add Source opcode handler
Date: Mon, 10 Jul 2023 19:40:23 +0000	[thread overview]
Message-ID: <168901802301.22137.10039217524697261844.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230629080735.525650-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 Thu, 29 Jun 2023 11:07:33 +0300 you wrote:
> This patch series adds the BASS control point handler
> for the Add Source operation.
> 
> If instructed by a Client through the Add Source opcode,
> the BASS Server attempts to synchronize to a Broadcast
> Source, by opening a btio channel.
> 
> [...]

Here is the summary with links:
  - [BlueZ,v3,1/2] btio: Add options for binding iso broadcast address
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=da85360a956f
  - [BlueZ,v3,2/2] shared/bass: Introduce Add Source opcode handler
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=8a8f8c143b18

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-07-10 19:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-29  8:07 [PATCH BlueZ v3 0/2] shared/bass: Introduce Add Source opcode handler Iulia Tanasescu
2023-06-29  8:07 ` [PATCH BlueZ v3 1/2] btio: Add options for binding iso broadcast address Iulia Tanasescu
2023-06-29  9:25   ` shared/bass: Introduce Add Source opcode handler bluez.test.bot
2023-06-29  8:07 ` [PATCH BlueZ v3 2/2] " Iulia Tanasescu
2023-07-10 19:40 ` 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=168901802301.22137.10039217524697261844.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.