From: Kaustabh Chakraborty <kauschluss@disroot.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Rob Herring <robh@kernel.org>, Conor Dooley <conor@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Sergey Lisov <sleirsgoevy@gmail.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Kaustabh Chakraborty <kauschluss@disroot.org>
Subject: Re: [PATCH 0/2] Add chip ID for Exynos7870 SoC
Date: Tue, 04 Feb 2025 19:29:59 +0000 [thread overview]
Message-ID: <e9d9388d0adacd5599c6c6f5b7f33f87@disroot.org> (raw)
In-Reply-To: <339ea40f-6bc7-42ad-a5c2-f57b3be8cc39@kernel.org>
On 2025-02-04 07:53, Krzysztof Kozlowski wrote:
> On 03/02/2025 21:32, Kaustabh Chakraborty wrote:
>> This patch series is a part of Exynos7870 upstreaming.
>>
>> Signed-off-by: Kaustabh Chakraborty <kauschluss@disroot.org>
>> ---
>> Kaustabh Chakraborty (2):
>> dt-bindings: hwinfo: samsung,exynos-chipid: add exynos7870-chipid compatible
>> soc: samsung: exynos-chipid: add support for exynos7870
>>
>> Documentation/devicetree/bindings/hwinfo/samsung,exynos-chipid.yaml | 1 +
>> drivers/soc/samsung/exynos-chipid.c | 1 +
>> 2 files changed, 2 insertions(+)
>
> When I asked to split, I said per subsystem. Soc is one subsystem.
> Everything targeting SoC should be in one patchset. get_maintainers.pl
> tells the name of the subsystem and its maintainers.
>
> If there is going to be resend/new version, combine patchsets for soc
> into one patchset (just like the example I gave last time).
Alright, so I'll move these patches to the one which has the devicetrees.
There's also a Documentation/devicetree/bindings/soc/ patch in
exynos7870-pmu-clocks [1]. The CLKOUT driver uses the compatible declared
in there, i.e., the CLKOUT driver depends on that commit. So, should it
stay there? Or...?
[1] https://lore.kernel.org/r/20250204-exynos7870-pmu-clocks-v1-0-a3030ae5bb53@disroot.org
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2025-02-04 19:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 20:32 [PATCH 0/2] Add chip ID for Exynos7870 SoC Kaustabh Chakraborty
2025-02-03 20:32 ` [PATCH 1/2] dt-bindings: hwinfo: samsung,exynos-chipid: add exynos7870-chipid compatible Kaustabh Chakraborty
2025-02-03 20:32 ` [PATCH 2/2] soc: samsung: exynos-chipid: add support for exynos7870 Kaustabh Chakraborty
2025-02-04 7:53 ` [PATCH 0/2] Add chip ID for Exynos7870 SoC Krzysztof Kozlowski
2025-02-04 18:13 ` Conor Dooley
2025-02-04 19:29 ` Kaustabh Chakraborty [this message]
2025-02-05 7:48 ` 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=e9d9388d0adacd5599c6c6f5b7f33f87@disroot.org \
--to=kauschluss@disroot.org \
--cc=alim.akhtar@samsung.com \
--cc=conor@kernel.org \
--cc=devicetree@vger.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=robh@kernel.org \
--cc=sleirsgoevy@gmail.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