public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: =?utf-8?b?RnLDqWTDqXJpYyBEYW5pcyA8ZnJlZGVyaWMuZGFuaXNAY29sbGFib3JhLmNvbT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2 1/4] shared/hfp: Add Operator name support
Date: Wed, 17 Sep 2025 13:30:06 +0000	[thread overview]
Message-ID: <175811580676.1623615.4409282341891803844.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250915163427.3589748-1-frederic.danis@collabora.com>

Hello:

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

On Mon, 15 Sep 2025 18:34:24 +0200 you wrote:
> Send AT+COPS=3,0 at the end of the SLC creation to set the format of
> the operator selection to long alphanumeric, then query the currently
> selected operator name from the AG.
> 
> Register +COPS handler to call the update_operator callback on event.
> ---
> v1->v2 : Move changes from patch 2 to fix unit/test-hfp
> 
> [...]

Here is the summary with links:
  - [BlueZ,v2,1/4] shared/hfp: Add Operator name support
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=b8d3e4c510b8
  - [BlueZ,v2,2/4] unit/test-hfp: Add Operator name test for HF
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=fb32f3a27fbd
  - [BlueZ,v2,3/4] shared/hfp: Add Call Line Identification support
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=889139e0a1af
  - [BlueZ,v2,4/4] unit/test-hfp: Add Call Line Identification test for HF
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=430b8b1b024b

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-09-17 13:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-15 16:34 [PATCH BlueZ v2 1/4] shared/hfp: Add Operator name support Frédéric Danis
2025-09-15 16:34 ` [PATCH BlueZ v2 2/4] unit/test-hfp: Add Operator name test for HF Frédéric Danis
2025-09-15 16:34 ` [PATCH BlueZ v2 3/4] shared/hfp: Add Call Line Identification support Frédéric Danis
2025-09-15 16:34 ` [PATCH BlueZ v2 4/4] unit/test-hfp: Add Call Line Identification test for HF Frédéric Danis
2025-09-15 18:05 ` [BlueZ,v2,1/4] shared/hfp: Add Operator name support bluez.test.bot
2025-09-17 13:30 ` 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=175811580676.1623615.4409282341891803844.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc==?utf-8?b?RnLDqWTDqXJpYyBEYW5pcyA8ZnJlZGVyaWMuZGFuaXNAY29sbGFib3JhLmNvbT4=?=@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