From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 1/2] battery: mark all battery DBus APIs non-experimental
Date: Thu, 05 Oct 2023 21:00:27 +0000 [thread overview]
Message-ID: <169653962798.16076.4314419735819907678.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ceaf8aa40e0967b01b86008b16a26bbb111a2cf6.1696524938.git.pav@iki.fi>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 5 Oct 2023 19:57:32 +0300 you wrote:
> Remove experimental marker from BatteryProvider1 and Battery1.Source.
>
> It's common that headsets send battery information via HFP, and often
> this is also the only way to get it. Pipewire/pulseaudio manage HFP,
> parse the battery commands, and use the BatteryProvider API if present
> to forward it. No problems with the API appeared here, and it's been
> experimental for a few years, so it's useful to enable it by default
> now.
>
> [...]
Here is the summary with links:
- [BlueZ,1/2] battery: mark all battery DBus APIs non-experimental
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=495a582675cf
- [BlueZ,2/2] doc: mark battery APIs non-experimental
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=85460c32d133
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:[~2023-10-05 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 16:57 [PATCH BlueZ 1/2] battery: mark all battery DBus APIs non-experimental Pauli Virtanen
2023-10-05 16:57 ` [PATCH BlueZ 2/2] doc: mark battery " Pauli Virtanen
2023-10-05 18:50 ` [BlueZ,1/2] battery: mark all battery DBus " bluez.test.bot
2023-10-05 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=169653962798.16076.4314419735819907678.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/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.