All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Vlad Pruteanu <vlad.pruteanu@nxp.com>
Cc: linux-bluetooth@vger.kernel.org, mihai-octavian.urzica@nxp.com,
	silviu.barbulescu@nxp.com, iulia.tanasescu@nxp.com,
	andrei.istodorescu@nxp.com, luiz.dentz@gmail.com
Subject: Re: [PATCH BlueZ 0/1] src/adapter: Check if device is connected before clean up
Date: Mon, 17 Jun 2024 14:00:29 +0000	[thread overview]
Message-ID: <171863282963.3187.16555705068218926939.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240617075934.154540-1-vlad.pruteanu@nxp.com>

Hello:

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

On Mon, 17 Jun 2024 10:59:33 +0300 you wrote:
> Broadcast sources are currently deleted on the clean up triggered
> by turning scan off. Thix fix prevents the removal of sources to
> which we are synced by also checking if the device that will be
> removed is connected (sources to which we are synced are already
> marked as connected).
> 
> Vlad Pruteanu (1):
>   src/adapter: Check if device is connected before clean up
> 
> [...]

Here is the summary with links:
  - [BlueZ,1/1] src/adapter: Check if device is connected before clean up
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=7ff745c2bd0c

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-06-17 14:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-17  7:59 [PATCH BlueZ 0/1] src/adapter: Check if device is connected before clean up Vlad Pruteanu
2024-06-17  7:59 ` [PATCH BlueZ 1/1] " Vlad Pruteanu
2024-06-17  9:44   ` bluez.test.bot
2024-06-17 14: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=171863282963.3187.16555705068218926939.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=andrei.istodorescu@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.