linux-kernel - Re: [PATCH v2 0/2] power: supply: bq27xxx: bug fixes

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 for Android: free password hash cracker in your pocket

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

Message-Id: <34413DBE-C225-4335-A0C8-B7E0DE53BF32@goldelico.com>
Date: Thu, 28 Aug 2025 22:11:59 +0200
From: "H. Nikolaus Schaller" <hns@...delico.com>
To: Andreas Kemnade <andreas@...nade.info>
Cc: Sebastian Reichel <sre@...nel.org>,
 Jerry Lv <Jerry.Lv@...s.com>,
 Pali Rohár <pali@...nel.org>,
 linux-pm@...r.kernel.org,
 linux-kernel@...r.kernel.org,
 letux-kernel@...nphoenux.org,
 stable@...r.kernel.org,
 kernel@...a-handheld.com
Subject: Re: [PATCH v2 0/2] power: supply: bq27xxx: bug fixes

> Am 28.08.2025 um 20:24 schrieb Andreas Kemnade <andreas@...nade.info>:
> 
> Am Sat, 23 Aug 2025 12:34:55 +0200
> schrieb "H. Nikolaus Schaller" <hns@...delico.com>:
> 
>> PATCH V2 2025-08-23 12:33:18:
>> Changes:
>> * improved commit description of main fix
>> * new patch: adds a restriction of historical no-battery-detection logic to the bq27000 chip
>> 
>> PATCH V1 2025-07-21 14:46:09:
>> 
>> 
>> H. Nikolaus Schaller (2):
>>  power: supply: bq27xxx: fix error return in case of no bq27000 hdq
>>    battery
>>  power: supply: bq27xxx: restrict no-battery detection to bq27000
>> 
> hmm, is the order correct? To me to be bisectable, should it be turned
> around? Maybe Sebastian just can do that while picking it.

Well, it is to decide which of the two fuel gauges fix first...

The bq27000 is working again after the first one and the bq27z561 is no longer influenced after the second.

BR,
Nikolaus