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 v2 0/2] client/player: Rework transport.select
Date: Tue, 28 Jan 2025 15:30:32 +0000	[thread overview]
Message-ID: <173807823275.3823183.6077030194795089397.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250127093004.19268-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 Mon, 27 Jan 2025 11:30:02 +0200 you wrote:
> This reworks transport.select not to require a local bluetoothctl endpoint
> in order to work, since the user should be able to use the command to
> select transports created by PipeWire, meaning that the audio server
> registers the broadcast sink endpoint, and no local endpoints are
> available.
> 
> Iulia Tanasescu (2):
>   client/player: Rework transport.select
>   client: Update transport.select documentation
> 
> [...]

Here is the summary with links:
  - [BlueZ,v2,1/2] client/player: Rework transport.select
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=6f284a920bcd
  - [BlueZ,v2,2/2] client: Update transport.select documentation
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=46fbbd600578

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-28 15:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-27  9:30 [PATCH BlueZ v2 0/2] client/player: Rework transport.select Iulia Tanasescu
2025-01-27  9:30 ` [PATCH BlueZ v2 1/2] " Iulia Tanasescu
2025-01-27 10:32   ` bluez.test.bot
2025-01-27  9:30 ` [PATCH BlueZ v2 2/2] client: Update transport.select documentation Iulia Tanasescu
2025-01-28 15:30 ` 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=173807823275.3823183.6077030194795089397.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.