From: patchwork-bot+bluetooth@kernel.org
To: Roman Smirnov <r.smirnov@omp.ru>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v7 1/2] shared/battery: improve the display of the charge level
Date: Mon, 17 Nov 2025 16:30:06 +0000 [thread overview]
Message-ID: <176339700651.3386490.5816332864802462652.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251114121140.102190-1-r.smirnov@omp.ru>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 14 Nov 2025 15:11:36 +0300 you wrote:
> The battery charge level may fluctuate due to uncalibrated
> sensors. Commit smooths out such fluctuations.
>
> The algorithm for determining uncalibrated sensors consists of
> finding the number of changes in charge direction (i.e., "spikes").
> If the number of spikes is zero, the device is charging or discharging.
> If there is one spike, it may mean that the device has started charging
> or has been disconnected from charging. If there are two or more spikes,
> this is a clear indication of an uncalibrated sensor.
>
> [...]
Here is the summary with links:
- [BlueZ,v7,1/2] shared/battery: improve the display of the charge level
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=c5d4a041483c
- [BlueZ,v7,2/2] unit: Add basic unit tests for battery charge handling
(no matching commit)
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-11-17 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 12:11 [PATCH BlueZ v7 1/2] shared/battery: improve the display of the charge level Roman Smirnov
2025-11-14 12:11 ` [PATCH BlueZ v7 2/2] unit: Add basic unit tests for battery charge handling Roman Smirnov
2025-11-14 13:45 ` [BlueZ,v7,1/2] shared/battery: improve the display of the charge level bluez.test.bot
2025-11-17 16: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=176339700651.3386490.5816332864802462652.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=r.smirnov@omp.ru \
/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.