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 v4 0/1] Bluetooth: ISO: Notify user space about failed bis connections
Date: Wed, 05 Jul 2023 23:00:24 +0000	[thread overview]
Message-ID: <168859802472.24898.8102885156352597251.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230703070238.4193-1-iulia.tanasescu@nxp.com>

Hello:

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

On Mon,  3 Jul 2023 10:02:37 +0300 you wrote:
> This patch makes it possible for the user to be informed if BIG sync
> has failed.
> 
> There are situations when certain procedures must be started in this
> case, like it is, for example, when a BASS Server fails to synchronize
> to a Broadcast source, as a result of a BASS Client writing the
> Add Source opcode to the control point characteristic. The BASS server
> should be able to detect if the sync was unsuccessful and it should
> send an appropriate GATT notification to the BASS client.
> 
> [...]

Here is the summary with links:
  - [v4,1/1] Bluetooth: ISO: Notify user space about failed bis connections
    https://git.kernel.org/bluetooth/bluetooth-next/c/5298a4d440cd

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-05 23:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-03  7:02 [PATCH v4 0/1] Bluetooth: ISO: Notify user space about failed bis connections Iulia Tanasescu
2023-07-03  7:02 ` [PATCH v4 1/1] " Iulia Tanasescu
2023-07-03  7:37   ` bluez.test.bot
2023-07-05 23:00 ` 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=168859802472.24898.8102885156352597251.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.