From: Sebastian Reichel <sre@kernel.org>
To: lh lin <lh.lin@mediatek.com>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
YJ Chiang <yj.chiang@mediatek.com>,
Lecopzer Chen <lecopzer.chen@mediatek.com>
Subject: Re: [PATCH] test_power: Fix battery_current initial value
Date: Wed, 29 Jul 2020 22:38:42 +0200 [thread overview]
Message-ID: <20200729203842.guuxxjogtduqgrqs@earth.universe> (raw)
In-Reply-To: <20200729121400.20960-1-lh.lin@mediatek.com>
[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]
Hi,
On Wed, Jul 29, 2020 at 08:14:00PM +0800, lh lin wrote:
> From: LH Lin <lh.lin@mediatek.com>
>
> Since default battery_status is POWER_SUPPLY_STATUS_DISCHARGING,
> we should change default battery_current to a negative value.
>
> Signed-off-by: LH Lin <lh.lin@mediatek.com>
> ---
Thanks, queued.
-- Sebastian
> drivers/power/supply/test_power.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/power/supply/test_power.c b/drivers/power/supply/test_power.c
> index 65c23ef6408d..4f29f0f096f5 100644
> --- a/drivers/power/supply/test_power.c
> +++ b/drivers/power/supply/test_power.c
> @@ -34,7 +34,7 @@ static int battery_technology = POWER_SUPPLY_TECHNOLOGY_LION;
> static int battery_capacity = 50;
> static int battery_voltage = 3300;
> static int battery_charge_counter = -1000;
> -static int battery_current = 1600;
> +static int battery_current = -1600;
>
> static bool module_initialized;
>
> --
> 2.18.0
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-07-29 20:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 12:14 [PATCH] test_power: Fix battery_current initial value lh lin
2020-07-29 20:38 ` Sebastian Reichel [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=20200729203842.guuxxjogtduqgrqs@earth.universe \
--to=sre@kernel.org \
--cc=lecopzer.chen@mediatek.com \
--cc=lh.lin@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=yj.chiang@mediatek.com \
/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;
as well as URLs for NNTP newsgroup(s).