linux-kernel - Re: [PATCH 49/57] power: Cancelling status charging notification.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120928021601.GH5040@lizard>
Date:	Thu, 27 Sep 2012 19:16:01 -0700
From:	Anton Vorontsov <anton.vorontsov@...aro.org>
To:	mathieu.poirier@...aro.org
Cc:	linux-kernel@...r.kernel.org, dwmw2@...radead.org
Subject: Re: [PATCH 49/57] power: Cancelling status charging notification.

On Tue, Sep 25, 2012 at 10:12:46AM -0600, mathieu.poirier@...aro.org wrote:
> From: "Mathieu J. Poirier" <mathieu.poirier@...aro.org>

No reasoning behind the change?

> Signed-off-by: Mathieu Poirier <mathieu.poirier@...aro.org>
> ---
>  drivers/power/abx500_chargalg.c |    2 --
>  1 files changed, 0 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/power/abx500_chargalg.c b/drivers/power/abx500_chargalg.c
> index ce58f20..4db0ef0 100644
> --- a/drivers/power/abx500_chargalg.c
> +++ b/drivers/power/abx500_chargalg.c
> @@ -641,10 +641,8 @@ static void abx500_chargalg_hold_charging(struct abx500_chargalg *di)
>  	abx500_chargalg_usb_en(di, false, 0, 0);
>  	abx500_chargalg_stop_safety_timer(di);
>  	abx500_chargalg_stop_maintenance_timer(di);
> -	di->charge_status = POWER_SUPPLY_STATUS_CHARGING;
>  	di->maintenance_chg = false;
>  	cancel_delayed_work(&di->chargalg_wd_work);
> -	power_supply_changed(&di->chargalg_psy);
>  }
>  
>  /**
> -- 
> 1.7.5.4
> 
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/