From: Krzysztof Kozlowski <krzk@kernel.org>
To: Umer Uddin <umer.uddin@mentallysanemainliners.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/1] Enable CMU_HSI1 for Exynos990
Date: Wed, 13 Aug 2025 10:01:04 +0200 [thread overview]
Message-ID: <c2e3aa26-7d9e-4423-9209-c882143310ce@kernel.org> (raw)
In-Reply-To: <20250528105821.158140-1-umer.uddin@mentallysanemainliners.org>
On 28/05/2025 12:58, Umer Uddin wrote:
> Hi all.
>
> This series enables a new clock block (CMU_HSI1) for the Exynos990
> SoC. This clock block provides clocks for the DesignWare MMC
> Controller, PCIE subsystem and UFS subsystem.
>
> This patch depends on the following series:
>
> [CMU_HSI1] https://lore.kernel.org/linux-samsung-soc/20250528105252.157533-1-umer.uddin@mentallysanemainliners.org/
>
I think dependency was not merged (received comments), so I will drop
this from my queue. If that is not accurate, anyway please resend once
dependency is ready/merged. Patch itself looked ok.
BTW, I take clock and SoC changes, so it is fine to send DTS with clock
dependency together. DTS should not be mixed with driver code for Greg's
subsystems, preferred not to mix for netdev.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-08-13 8:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 10:58 Umer Uddin
2025-05-28 10:58 ` [PATCH v1 1/1] arm64: dts: exynos990: Add CMU_HSI1 node Umer Uddin
2025-05-28 12:37 ` [PATCH v1 0/1] Enable CMU_HSI1 for Exynos990 Rob Herring (Arm)
2025-08-13 8:01 ` 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=c2e3aa26-7d9e-4423-9209-c882143310ce@kernel.org \
--to=krzk@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@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=umer.uddin@mentallysanemainliners.org \
/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®