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 1/2] shared/hfp: Add function to get multiparty call status
Date: Thu, 15 Jan 2026 21:40:07 +0000 [thread overview]
Message-ID: <176851320779.4178208.3244529374824613467.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251224144545.211533-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 Wed, 24 Dec 2025 15:45:44 +0100 you wrote:
> ---
> src/shared/hfp.c | 20 ++++++++++++++++++++
> src/shared/hfp.h | 1 +
> 2 files changed, 21 insertions(+)
Here is the summary with links:
- [BlueZ,1/2] shared/hfp: Add function to get multiparty call status
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=22eca40e5ceb
- [BlueZ,2/2] audio/hfp-hf: Update multiparty status on call creation
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=5e50b9353ff7
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:[~2026-01-15 21:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-24 14:45 [PATCH BlueZ 1/2] shared/hfp: Add function to get multiparty call status Frédéric Danis
2025-12-24 14:45 ` [PATCH BlueZ 2/2] audio/hfp-hf: Update multiparty status on call creation Frédéric Danis
2025-12-24 15:36 ` [BlueZ,1/2] shared/hfp: Add function to get multiparty call status bluez.test.bot
2026-01-15 21: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=176851320779.4178208.3244529374824613467.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 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.