[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <08558b39-bf69-43a7-8f55-064995221099@uclouvain.be>
Date: Mon, 2 Dec 2024 15:54:10 +0100
From: Thomas Antoine <t.antoine@...ouvain.be>
To: Krzysztof Kozlowski <krzk@...nel.org>, Sebastian Reichel
<sre@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Dimitri Fedrau <dima.fedrau@...il.com>,
Catalin Marinas <catalin.marinas@....com>, Will Deacon <will@...nel.org>,
Peter Griffin <peter.griffin@...aro.org>,
Alim Akhtar <alim.akhtar@...sung.com>
Cc: linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org
Subject: Re: [PATCH 3/4] arm64: defconfig: enable Maxim max1720x driver
On 12/2/24 14:40, Krzysztof Kozlowski wrote:
> On 02/12/2024 14:07, Thomas Antoine via B4 Relay wrote:
>> From: Thomas Antoine <t.antoine@...ouvain.be>
>> CONFIG_BATTERY_QCOM_BATTMGR=m
>> CONFIG_BATTERY_SBS=m
>> CONFIG_BATTERY_BQ27XXX=y
>> +CONFIG_BATTERY_MAX1720X=m
>> CONFIG_BATTERY_MAX17042=m
>
> Are you sure this is placed according to savedefconfig order?
I ran menuconfig and it put CONFIG_BATTERY_MAX1720X below
CONFIG_BATTERY_MAX17042 so I think it is an error on my part.
Will fix in v2.
Best regards,
Thomas Antoine
Powered by blists - more mailing lists