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,
	luiz.dentz@gmail.com
Subject: Re: [PATCH BlueZ v2 0/1] btio: Allow binding a bcast listener before accept
Date: Tue, 24 Oct 2023 18:50:22 +0000	[thread overview]
Message-ID: <169817342283.13534.14599969182820704167.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231024110430.3323-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, 24 Oct 2023 14:04:29 +0300 you wrote:
> This patch adds btio support for binding a PA sync io to a number of
> BISes, before proceeding with BIG Create Sync.
> 
> This depends on the kernel update introduced by
> [PATCH v3 0/1] Bluetooth: ISO: Allow binding a PA sync socket.
> 
> This patch version fixes scan-build warning.
> 
> [...]

Here is the summary with links:
  - [BlueZ,v2,1/1] btio: Allow binding a bcast listener before accept
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=00fdb61d5616

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-10-24 18:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-24 11:04 [PATCH BlueZ v2 0/1] btio: Allow binding a bcast listener before accept Iulia Tanasescu
2023-10-24 11:04 ` [PATCH BlueZ v2 1/1] " Iulia Tanasescu
2023-10-24 12:09   ` bluez.test.bot
2023-10-24 18:50 ` patchwork-bot+bluetooth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-19 14:52 [PATCH BlueZ v2 0/1] " Iulia Tanasescu

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=169817342283.13534.14599969182820704167.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 \
    --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.