linux-kernel - Re: [PATCH 3/4] arm64: defconfig: add S32G RTC module 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <a9833ffb-d073-45b6-b65d-5492cab631b5@kernel.org>
Date: Wed, 18 Sep 2024 10:10:44 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Ciprian Marian Costea <ciprianmarian.costea@....nxp.com>,
 Alexandre Belloni <alexandre.belloni@...tlin.com>,
 Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Conor Dooley <conor+dt@...nel.org>, Catalin Marinas
 <catalin.marinas@....com>, Will Deacon <will@...nel.org>
Cc: linux-rtc@...r.kernel.org, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
 NXP S32 Linux Team <s32@....com>
Subject: Re: [PATCH 3/4] arm64: defconfig: add S32G RTC module support

On 18/09/2024 10:02, Ciprian Marian Costea wrote:
> On 9/17/2024 8:36 PM, Krzysztof Kozlowski wrote:
>> On 11/09/2024 09:00, Ciprian Costea wrote:
>>> From: Ciprian Marian Costea <ciprianmarian.costea@....nxp.com>
>>>
>>> This patch enables CONFIG_RTC_DRV_S32G as module by default.
>>
>> We see this from the diff. We do not see why we would like this.
>>
>> Best regards,
>> Krzysztof
>>
> 
> Hello Krzysztof,
> 
> Thanks for your feedback.
> 
> I can see how not providing any information in the commit message 
> regarding why this config is important for S32G2/S32G3 SoCs is not ideal.
> 
> Considering this, if I would add such information, would it be 
> acceptable to enable this config as module ? Or should I drop this 
> commit instead ?
> 
> My decision to enable it as module by default was also influenced by 
> other similar RTC related configs, which are present in 'defconfig'.
> 

I don't object the patch contents itself. I want some sort of
explanation in the commit msg. Each commit msg is supposed to answer to
"why?" (unless it is obvious) and the answer is for example that
platform foo bar uses it. See some examples in git history.

Best regards,
Krzysztof