linux-kernel - Re: [PATCH v6 0/2] MAX77759 Fuel Gauge driver support

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] [day] [month] [year] [list]

Message-ID: <cd07660f196ce5686b32a67fa5a4edf5dd70dbc2.camel@linaro.org>
Date: Tue, 06 Jan 2026 17:08:32 +0000
From: André Draszik <andre.draszik@...aro.org>
To: Thomas Antoine <t.antoine@...ouvain.be>
Cc: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
  Conor Dooley <conor+dt@...nel.org>, Sebastian Reichel <sre@...nel.org>,
 Peter Griffin	 <peter.griffin@...aro.org>, linux-kernel@...r.kernel.org, 
	linux-pm@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v6 0/2] MAX77759 Fuel Gauge driver support

Hi Thomas,

On Tue, 2026-01-06 at 17:54 +0100, Thomas Antoine wrote:
> Hi,
> 
> > [...] 
> > Are you still working on this? Are you planning to send out a new version?
> 
> Really sorry for the long time since I sent anything. I had some personal
> issues and had to focus on work so I could not work on this.
> 
> Moreover, after rechecking the files, I noticed that the support for the
> MAX77759 should most likely go in the max17042_battery.c file. There is
> already support for multiple chips (e.g. max77705, max7779849) and when
> I looked into it a while ago, most of the support of my last patch was
> present with some things more.
> I don't know how I did not notice this when I first started working on this.
> 
> I can rework this patch and send it by the end of the week as the change
> requests were pretty light.
> However, I think the cleaner course of action is for me to attempt to
> integrate changes into the max17042 file and see if anything causes
> problems which would warrant a new driver. I think I can take the free
> time to do this by the end of the month.
> 
> What do you think?

Thanks for the detailed answer, much appreciated!

I'm always up for cleaner solutions, and unless somebody else has a
compelling reason to not follow your new outlined approach, I'd
say go for it :-)

Happy new year to you too!

Cheers,
Andre'