From: Krzysztof Kozlowski <krzk@kernel.org>
To: Tudor Ambarus <tudor.ambarus@linaro.org>,
Alim Akhtar <alim.akhtar@samsung.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
peter.griffin@linaro.org, andre.draszik@linaro.org,
willmcvicker@google.com, kernel-team@android.com
Subject: Re: [PATCH 0/4] soc: samsung: exynos-chipid: trivial updates to simplify code
Date: Wed, 19 Nov 2025 13:12:13 +0100 [thread overview]
Message-ID: <782da69d-d118-4d7c-baf7-a8164fc550b8@kernel.org> (raw)
In-Reply-To: <20251112-chipid-trivial-v1-0-ec2dea03bd83@linaro.org>
On 12/11/2025 09:48, Tudor Ambarus wrote:
> Trivial patches to simplify code done while handling the GS101 chipid
> support. Compile tested only.
>
> Signed-off-by: Tudor Ambarus <tudor.ambarus@linaro.org>
> ---
> Tudor Ambarus (4):
> soc: samsung: exynos-chipid: prepend exynos_ to a method's name
> soc: samsung: exynos-chipid: downgrade dev_info to dev_dbg for soc info
> soc: samsung: exynos-chipid: simplify with dev_err_probe
> soc: samsung: exynos-chipid: use devm action to unregister soc device
>
AFAIU, this patchset is superseded with v2 using OTP bindings, so I am
dropping it.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-11-19 12:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 8:48 [PATCH 0/4] soc: samsung: exynos-chipid: trivial updates to simplify code Tudor Ambarus
2025-11-12 8:48 ` [PATCH 1/4] soc: samsung: exynos-chipid: prepend exynos_ to a method's name Tudor Ambarus
2025-11-12 8:48 ` [PATCH 2/4] soc: samsung: exynos-chipid: downgrade dev_info to dev_dbg for soc info Tudor Ambarus
2025-11-12 8:48 ` [PATCH 3/4] soc: samsung: exynos-chipid: simplify with dev_err_probe Tudor Ambarus
2025-11-12 8:48 ` [PATCH 4/4] soc: samsung: exynos-chipid: use devm action to unregister soc device Tudor Ambarus
2025-11-18 14:01 ` [PATCH 0/4] soc: samsung: exynos-chipid: trivial updates to simplify code Tudor Ambarus
2025-11-19 12:12 ` Krzysztof Kozlowski [this message]
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=782da69d-d118-4d7c-baf7-a8164fc550b8@kernel.org \
--to=krzk@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=andre.draszik@linaro.org \
--cc=kernel-team@android.com \
--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=tudor.ambarus@linaro.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;
as well as URLs for NNTP newsgroup(s).