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: <6f0761a6-5f49-42e2-9b79-3e04c9d259a4@redhat.com>
Date: Wed, 27 Mar 2024 11:36:02 +0100
From: Hans de Goede <hdegoede@...hat.com>
To: Sebastian Reichel <sebastian.reichel@...labora.com>,
 Sebastian Reichel <sre@...nel.org>, Konrad Dybcio <konradybcio@...nel.org>,
 Thomas Weißschuh <linux@...ssschuh.net>
Cc: linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] power: supply: test-power: implement charge_behaviour
 property

Hi Sebastian,

On 3/26/24 8:50 PM, Sebastian Reichel wrote:
> 
> On Wed, 06 Mar 2024 20:37:04 +0100, Thomas Weißschuh wrote:
>> To validate the special formatting of the "charge_behaviour" sysfs
>> property add it to the example driver.
>>
>>
> 
> Applied, thanks!
> 
> [1/1] power: supply: test-power: implement charge_behaviour property
>       commit: 070c1470ae24317e7b19bd3882b300b6d69922a4

Does this mean that you've also applied patches 1-3 of:
"[PATCH v2 0/4] power: supply: core: align charge_behaviour format with docs" ?

Because this is a new version of 4/4 of that series and I think
that the new test may depend on the fixes from patches 1-3
of that series (which I'm reviewing now).

Regards,

Hans



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ