[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e9d9388d0adacd5599c6c6f5b7f33f87@disroot.org>
Date: Tue, 04 Feb 2025 19:29:59 +0000
From: Kaustabh Chakraborty <kauschluss@...root.org>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: Rob Herring <robh@...nel.org>, Conor Dooley <conor@...nel.org>, Alim
Akhtar <alim.akhtar@...sung.com>, Sergey Lisov <sleirsgoevy@...il.com>,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org, Kaustabh
Chakraborty <kauschluss@...root.org>
Subject: Re: [PATCH 0/2] Add chip ID for Exynos7870 SoC
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@...root.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
Powered by blists - more mailing lists