From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ciprian Marian Costea <ciprianmarian.costea@oss.nxp.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Cc: linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
NXP S32 Linux Team <s32@nxp.com>
Subject: Re: [PATCH 3/4] arm64: defconfig: add S32G RTC module support
Date: Wed, 18 Sep 2024 10:10:44 +0200 [thread overview]
Message-ID: <a9833ffb-d073-45b6-b65d-5492cab631b5@kernel.org> (raw)
In-Reply-To: <1dffa158-0608-4480-9281-3b891acc8c6b@oss.nxp.com>
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@oss.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
next prev parent reply other threads:[~2024-09-18 8:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 7:00 [PATCH 0/4] add NXP RTC driver support for S32G2/S32G3 SoCs Ciprian Costea
2024-09-11 7:00 ` [PATCH 1/4] dt-bindings: rtc: add schema for NXP " Ciprian Costea
2024-09-11 18:21 ` Conor Dooley
2024-09-12 10:50 ` Ciprian Marian Costea
2024-09-12 11:27 ` Conor Dooley
2024-09-12 13:02 ` Ciprian Marian Costea
2024-09-12 12:26 ` Alexandre Belloni
2024-09-12 12:36 ` Ciprian Marian Costea
2024-09-12 14:03 ` Alexandre Belloni
2024-09-17 7:21 ` Ciprian Marian Costea
2024-09-17 12:37 ` Conor Dooley
2024-09-17 13:01 ` Alexandre Belloni
2024-09-11 18:22 ` Conor Dooley
2024-09-12 10:55 ` Ciprian Marian Costea
2024-09-12 11:13 ` Conor Dooley
2024-09-12 12:00 ` Ciprian Marian Costea
2024-09-12 12:12 ` Conor Dooley
2024-09-12 12:16 ` Ciprian Marian Costea
2024-09-11 7:00 ` [PATCH 2/4] rtc: s32g: add NXP S32G2/S32G3 SoC support Ciprian Costea
2024-09-12 4:41 ` kernel test robot
2024-09-13 11:58 ` kernel test robot
2024-09-17 17:40 ` Krzysztof Kozlowski
2024-09-18 7:51 ` Ciprian Marian Costea
2024-09-18 10:26 ` Alexandre Belloni
2024-09-18 15:08 ` Ciprian Marian Costea
2024-09-11 7:00 ` [PATCH 3/4] arm64: defconfig: add S32G RTC module support Ciprian Costea
2024-09-17 17:36 ` Krzysztof Kozlowski
2024-09-18 8:02 ` Ciprian Marian Costea
2024-09-18 8:10 ` Krzysztof Kozlowski [this message]
2024-09-11 7:00 ` [PATCH 4/4] MAINTAINERS: add MAINTAINER for S32G2/S32G3 RTC driver Ciprian Costea
2024-09-17 17:37 ` Krzysztof Kozlowski
2024-09-18 8:13 ` Ciprian Marian Costea
2024-09-18 10:36 ` Krzysztof Kozlowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a9833ffb-d073-45b6-b65d-5492cab631b5@kernel.org \
--to=krzk@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=catalin.marinas@arm.com \
--cc=ciprianmarian.costea@oss.nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s32@nxp.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).