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]
Date:   Fri, 26 Oct 2018 09:57:05 +0800
From:   Baolin Wang <baolin.wang@...aro.org>
To:     Sebastian Reichel <sebastian.reichel@...labora.com>
Cc:     Rob Herring <robh+dt@...nel.org>,
        Mark Rutland <mark.rutland@....com>,
        Linux PM list <linux-pm@...r.kernel.org>,
        DTML <devicetree@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>, yuanjiang.yu@...soc.com,
        Mark Brown <broonie@...nel.org>,
        Craig Tatlor <ctatlor97@...il.com>,
        Linus Walleij <linus.walleij@...aro.org>
Subject: Re: [PATCH v6 1/6] dt-bindings: power: Introduce one property to
 present the battery internal resistance

On 26 October 2018 at 04:13, Sebastian Reichel
<sebastian.reichel@...labora.com> wrote:
> Hi Baolin,
>
> On Thu, Oct 25, 2018 at 10:01:55AM +0800, Baolin Wang wrote:
>> Hi Sebastian,
>>
>> On 22 October 2018 at 15:43, Baolin Wang <baolin.wang@...aro.org> wrote:
>> > The internal resistance of a battery is not a constant in its life cycle,
>> > this varies over the age of the battery or temperature and so on. But we
>> > just want use one constant battery internal resistance to estimate the
>> > battery capacity. Thus this patch introduces one property to present
>> > the battery factory internal resistance for battery information.
>> >
>> > Signed-off-by: Baolin Wang <baolin.wang@...aro.org>
>> > Reviewed-by: Linus Walleij <linus.walleij@...aro.org>
>> > ---
>> > Changes from v5:
>> >  - None.
>> >
>> > Changes from v4:
>> >  - None.
>> >
>> > Changes from v3:
>> >  - Split binding into one separate patch.
>> >  - Add LinusW reviewed tag.
>> >
>> > Changes from v2:
>> >  - Rename the property.
>> >  - Improve the commit message.
>> >
>> > Changes from v1:
>> >  - New patch in v2.
>> > ---
>>
>> I think this v6 patch set have addressed your comments on v5, so could
>> you apply this patch set if there are no other comments? I hope this
>> driver can be merged into 4.20 finally. Thanks.
>
> Everything looks fine to me. I will merge this directly after the
> 4.20 merge window has been closed and linux-next is open again.
> I'm not merging non-trivial, non-bugfix patches this lates during the
> release process.

Understood. Thanks Sebastian.

-- 
Baolin Wang
Best Regards

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ