From: Conor Dooley <conor@kernel.org>
To: Nicolas Pitre <npitre@baylibre.com>
Cc: Julien Panis <jpanis@baylibre.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Zhang Rui <rui.zhang@intel.com>,
Lukasz Luba <lukasz.luba@arm.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH v5 1/6] dt-bindings: thermal: mediatek: Rename thermal zone definitions for MT8186 and MT8188
Date: Mon, 27 May 2024 22:07:28 +0100 [thread overview]
Message-ID: <20240527-reclusive-elderly-5b2d6bfee6b9@spud> (raw)
In-Reply-To: <r9q3n5n4-4pqn-53so-4n65-33p432530793@onlyvoer.pbz>
[-- Attachment #1.1: Type: text/plain, Size: 1347 bytes --]
On Mon, May 27, 2024 at 04:57:15PM -0400, Nicolas Pitre wrote:
> On Mon, 27 May 2024, Conor Dooley wrote:
> > > Would Russell's suggestion be acceptable for you ?
> > > I mean, this one:
> > > https://lore.kernel.org/all/ZlDMNkdE2jmFgD8B@shell.armlinux.org.uk/
> > >
> > > I could implement it, but before submitting it I would like to make
> > > sure that it suits everyone.
> >
> > How's that going to work? MT8188_AP_GPU1 currently means 1, after your
> > series it means 2.
> > You're gonna need to pick a different naming for the new defines to
> > avoid that. Additionally, why even delete the old ones? Just define
> > new names with the same numbering and you don't need to worry about
> > any compatibility issues.
>
> Isn't this making a mountain out of a molehill here?
>
> Seriously... none of this was present in a released kernel. The naming
> can be adjusted "atomically" so compilation doesn't break, and
> it is within maintainers' discretion to bypass the checkpatch warning in
> such particular case.
If that's the case, then great. Provide a fixes tag, and a better commit
message than "Use thermal zone names that make more sense." that
actually explains why it is okay to change the definitions. There'd've
been neither mountain nor molehill were a sufficient commit message
provided.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-05-27 21:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 9:04 [PATCH v5 0/6] Mediatek thermal sensor driver support for MT8186 and MT8188 Julien Panis
2024-05-24 9:04 ` [PATCH v5 1/6] dt-bindings: thermal: mediatek: Rename thermal zone definitions " Julien Panis
2024-05-24 18:24 ` Conor Dooley
2024-05-24 18:27 ` Conor Dooley
2024-05-27 15:25 ` Julien Panis
2024-05-27 17:28 ` Conor Dooley
2024-05-27 20:57 ` Nicolas Pitre
2024-05-27 21:07 ` Conor Dooley [this message]
2024-05-27 8:14 ` Julien Panis
2024-05-24 9:04 ` [PATCH v5 2/6] thermal/drivers/mediatek/lvts_thermal: Use renamed " Julien Panis
2024-05-24 9:04 ` [PATCH v5 3/6] arm64: dts: mediatek: mt8186: add lvts definitions Julien Panis
2024-05-24 9:04 ` [PATCH v5 4/6] arm64: dts: mediatek: mt8186: add default thermal zones Julien Panis
2024-05-24 9:04 ` [PATCH v5 5/6] arm64: dts: mediatek: mt8188: add lvts definitions Julien Panis
2024-05-24 9:04 ` [PATCH v5 6/6] arm64: dts: mediatek: mt8188: add default thermal zones Julien Panis
2024-05-24 17:04 ` [PATCH v5 0/6] Mediatek thermal sensor driver support for MT8186 and MT8188 Nicolas Pitre
2024-05-24 17:19 ` Russell King (Oracle)
2024-05-27 8:38 ` Julien Panis
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=20240527-reclusive-elderly-5b2d6bfee6b9@spud \
--to=conor@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jpanis@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=npitre@baylibre.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=rui.zhang@intel.com \
/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