public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: =?utf-8?b?WWFvIFdlaSAo6a2P6YqY5bu3KSA8eWFvLndlaUBjYW5vbmljYWwuY29tPg==?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 0/1] policy: fix HSP/HFP reconnection
Date: Wed, 09 Apr 2025 14:40:32 +0000	[thread overview]
Message-ID: <174420963250.2845819.13289870998224229498.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250401020221.119615-1-yao.wei@canonical.com>

Hello:

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

On Tue,  1 Apr 2025 10:02:20 +0800 you wrote:
> This patch was regarding to https://github.com/bluez/bluez/issues/1069.
> 
> The previous patch did not fix the issue, as I was testing it with Apple
> AirPods Pro 2 and it automatically reconnects HSP/HFP after A2DP is
> connected for about 25 seconds, and I assume the patch worked for me.
> Some other devices I tested did not exhibit such behavior (Jabra Speak2
> 55 UC).  This patch was tested against both these devices, and both
> cases with NVIDIA GPU enabled and disabled.
> 
> [...]

Here is the summary with links:
  - [BlueZ,1/1] policy: fix HSP/HFP reconnection
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=0b3d49f4e030

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-04-09 14:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-01  2:02 [PATCH BlueZ 0/1] policy: fix HSP/HFP reconnection Yao Wei (魏銘廷)
2025-04-01  2:02 ` [PATCH BlueZ 1/1] " Yao Wei (魏銘廷)
2025-04-01  3:55   ` bluez.test.bot
2025-04-09 14:40 ` 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=174420963250.2845819.13289870998224229498.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc==?utf-8?b?WWFvIFdlaSAo6a2P6YqY5bu3KSA8eWFvLndlaUBjYW5vbmljYWwuY29tPg==?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
    --cc=linux-bluetooth@vger.kernel.org \
    /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