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 0/1] Bluetooth: ISO: Avoid creating child socket if PA sync is terminating
Date: Fri, 08 Dec 2023 15:10:24 +0000	[thread overview]
Message-ID: <170204822462.3151.17183097040428735461.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231205161140.2855-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 Tue,  5 Dec 2023 18:11:39 +0200 you wrote:
> When a PA sync socket is closed, the associated hcon is also unlinked
> and cleaned up. If there are no other hcons marked with the
> HCI_CONN_PA_SYNC flag, HCI_OP_LE_PA_TERM_SYNC is sent to controller.
> 
> Between the time of the command and the moment PA sync is terminated
> in controller, residual BIGInfo reports might continue to come.
> This causes a new PA sync hcon to be added, and a new socket to be
> notified to user space.
> 
> [...]

Here is the summary with links:
  - [1/1] Bluetooth: ISO: Avoid creating child socket if PA sync is terminating
    https://git.kernel.org/bluetooth/bluetooth-next/c/1581c2ec0214

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-12-08 15:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05 16:11 [PATCH 0/1] Bluetooth: ISO: Avoid creating child socket if PA sync is terminating Iulia Tanasescu
2023-12-05 16:11 ` [PATCH 1/1] " Iulia Tanasescu
2023-12-05 17:01   ` bluez.test.bot
2023-12-08 15:10 ` patchwork-bot+bluetooth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-29 16:28 [PATCH 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=170204822462.3151.17183097040428735461.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.