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/1] bass: Register bap attached/detached callbacks
Date: Wed, 12 Feb 2025 21:40:34 +0000	[thread overview]
Message-ID: <173939643499.667348.6080977145685830613.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250211141936.23372-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 Tue, 11 Feb 2025 16:19:34 +0200 you wrote:
> This removes the bass_bcast_probe and bass_bcast_remove APIs, in order to
> decouple the BASS and BAP plugins.
> 
> Instead, since the BASS Server (BAP Scan Delegator) implementation needs
> to reference the bap session, BASS registers bap attached/detached
> callbacks with shared/bap.
> 
> [...]

Here is the summary with links:
  - [BlueZ,1/1] bass: Register bap attached/detached callbacks
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=8fa5584e5632

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-02-12 21:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-11 14:19 [PATCH BlueZ 0/1] bass: Register bap attached/detached callbacks Iulia Tanasescu
2025-02-11 14:19 ` [PATCH BlueZ 1/1] " Iulia Tanasescu
2025-02-11 17:39   ` bluez.test.bot
2025-02-12 21: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=173939643499.667348.6080977145685830613.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.