From: patchwork-bot+bluetooth@kernel.org
To: Arun Raghavan <arun@asymptotic.io>
Cc: linux-bluetooth@vger.kernel.org, sanchayan@asymptotic.io
Subject: Re: [PATCH BlueZ v2 0/3] Fixes for re-connection issues with ASHA profile
Date: Wed, 23 Apr 2025 21:00:28 +0000 [thread overview]
Message-ID: <174544202825.2766467.9984202176484065289.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250423150742.319463-1-arun@asymptotic.io>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 23 Apr 2025 11:07:39 -0400 you wrote:
> This set of two patches fixes re-connection issues for the ASHA profile.
>
> v2:
> * Incorporate feedback from review -- reset state in
> `bt_asha_reset()`, and use "attach" instead of "probe"
> * Add a minor renaming patch for readability
>
> [...]
Here is the summary with links:
- [BlueZ,v2,1/3] profiles/audio: asha: Reset state on disconnect
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=918432b2c68d
- [BlueZ,v2,2/3] profiles/audio: asha: Only expose device after we have attributes
(no matching commit)
- [BlueZ,v2,3/3] shared: asha: Use a more descriptive name for the state callback
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=629672307f6c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-04-23 20:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 15:07 [PATCH BlueZ v2 0/3] Fixes for re-connection issues with ASHA profile Arun Raghavan
2025-04-23 15:07 ` [PATCH BlueZ v2 1/3] profiles/audio: asha: Reset state on disconnect Arun Raghavan
2025-04-23 15:07 ` [PATCH BlueZ v2 2/3] profiles/audio: asha: Only expose device after we have attributes Arun Raghavan
2025-04-23 15:07 ` [PATCH BlueZ v2 3/3] shared: asha: Use a more descriptive name for the state callback Arun Raghavan
2025-04-23 21: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=174544202825.2766467.9984202176484065289.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=arun@asymptotic.io \
--cc=linux-bluetooth@vger.kernel.org \
--cc=sanchayan@asymptotic.io \
/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