From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: "André Draszik" <andre.draszik@linaro.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Alim Akhtar" <alim.akhtar@samsung.com>,
"Peter Griffin" <peter.griffin@linaro.org>,
"Srinivas Kandagatla" <srini@kernel.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
semen.protsenko@linaro.org, willmcvicker@google.com,
kernel-team@android.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/5] soc: samsung: exynos-chipid: rename method
Date: Tue, 23 Dec 2025 12:14:49 +0200 [thread overview]
Message-ID: <51565d98-ac0a-44f4-af30-6d42b68661da@linaro.org> (raw)
In-Reply-To: <bf1bca0af63f161afe351cb0e449896cec11cdcc.camel@linaro.org>
On 12/23/25 11:55 AM, André Draszik wrote:
> On Mon, 2025-12-22 at 16:30 +0000, Tudor Ambarus wrote:
>> s/product_id_to_soc_id/exynos_product_id_to_name.
>> Prepend exynos_ to avoid name space pollution. The method translates the
>> product id to a name, rename the method to make that clear. While
>> touching the code where it is called, add a blank line for readability
>> purposes.
>>
>> Signed-off-by: Tudor Ambarus <tudor.ambarus@linaro.org>
>> ---
>> drivers/soc/samsung/exynos-chipid.c | 5 +++--
>> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> I'm not sure this change helps with anything, in particular as the
> return value is used to assign to soc_id, but in case it gets applied:
what drove me to do the rename, and prepend exynos_ to the method name,
was that IP specific drivers should not use generic names for methods ->
those shall be left for the core.
Now about the s/soc_id/name, you're right, I could kept soc_id to align
with the soc interface. Happy to resend for this if you think it is worth
it, or drop altogether.
>
> Reviewed-by: André Draszik <andre.draszik@linaro.org>
Cheers,
ta
next prev parent reply other threads:[~2025-12-23 10:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 16:30 [PATCH v4 0/5] soc: samsung: exynos-chipid: add gs101 support Tudor Ambarus
2025-12-22 16:30 ` [PATCH v4 1/5] dt-bindings: nvmem: add google,gs101-otp Tudor Ambarus
2025-12-22 16:30 ` [PATCH v4 2/5] soc: samsung: exynos-chipid: rename method Tudor Ambarus
2025-12-23 9:55 ` André Draszik
2025-12-23 10:14 ` Tudor Ambarus [this message]
2025-12-22 16:30 ` [PATCH v4 3/5] soc: samsung: exynos-chipid: downgrade dev_info to dev_dbg for soc info Tudor Ambarus
2025-12-22 16:30 ` [PATCH v4 4/5] soc: samsung: exynos-chipid: add google,gs101-otp support Tudor Ambarus
2025-12-23 9:56 ` André Draszik
2025-12-23 10:18 ` André Draszik
2025-12-23 11:23 ` André Draszik
2025-12-22 16:30 ` [PATCH v4 5/5] arm64: dts: exynos: gs101: add OTP node Tudor Ambarus
2025-12-23 10:01 ` André Draszik
2025-12-28 11:32 ` (subset) [PATCH v4 0/5] soc: samsung: exynos-chipid: add gs101 support Krzysztof Kozlowski
2025-12-28 11:33 ` 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=51565d98-ac0a-44f4-af30-6d42b68661da@linaro.org \
--to=tudor.ambarus@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=andre.draszik@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel-team@android.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=robh@kernel.org \
--cc=semen.protsenko@linaro.org \
--cc=srini@kernel.org \
--cc=willmcvicker@google.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
all inboxes | Powered by JetHome®