public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Remi Pommarel <repk@triplefau.lt>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2] policy: Fix service retry counters reset
Date: Tue, 27 May 2025 21:20:27 +0000	[thread overview]
Message-ID: <174838082775.1782235.17410109323459610043.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250527134521.4942-1-repk@triplefau.lt>

Hello:

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

On Tue, 27 May 2025 15:45:21 +0200 you wrote:
> Control and Target retries counter were reset when service state
> goes from CONNECTED to DISCONNECTED, but usually an extra DISCONNECTING
> state is reached before going to DISCONNECTED. This causes retry counter
> to not being reset in this case, leading to service not being able to
> initialize on next connection. Source, sink and HS retry counter were
> only reset when limit was reached, moreover HS timer was not removed on
> CONNECTED state.
> 
> [...]

Here is the summary with links:
  - [BlueZ,v2] policy: Fix service retry counters reset
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=2a552b93de8b

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-05-27 21:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-27 13:45 [PATCH BlueZ v2] policy: Fix service retry counters reset Remi Pommarel
2025-05-27 15:28 ` [BlueZ,v2] " bluez.test.bot
2025-05-27 21:20 ` 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=174838082775.1782235.17410109323459610043.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=repk@triplefau.lt \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox