From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Tudor Ambarus" <tudor.ambarus@linaro.org>,
"Peter Griffin" <peter.griffin@linaro.org>,
"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>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Will Deacon" <will@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, willmcvicker@google.com,
kernel-team@android.com
Subject: Re: [PATCH v4 0/3] arm64: dts: exynos: gs101: add cpufreq support
Date: Mon, 20 Oct 2025 09:07:50 +0200 [thread overview]
Message-ID: <8b095395-8c09-45ba-8dcb-48cd81b8c0e0@kernel.org> (raw)
In-Reply-To: <20250924-acpm-dvfs-dt-v4-0-3106d49e03f5@linaro.org>
On 24/09/2025 17:14, Tudor Ambarus wrote:
> Define the CPU clocks and OPPs.
>
> Patch #2 has a dependency on the ACPM clock bindings sent at:
> https://lore.kernel.org/linux-samsung-soc/20250924-acpm-clk-v5-1-4cca1fadd00d@linaro.org/T/#u
>
> Thanks,
> ta
Please stop CC-ing address kernel-team@android.com. I receive bounced
from them:
---
Your email to group kernel-team@android.com was rejected due to spam
classification.
---
Cc only public addresses, not internal ones. If any kernel team needs
these patches, they can easily set lore/lei tracking.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-10-20 7:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 15:14 Tudor Ambarus
2025-09-24 15:14 ` [PATCH v4 1/3] arm64: dts: exynos: gs101: add #clock-cells to the ACPM protocol node Tudor Ambarus
2025-09-24 15:14 ` [PATCH v4 2/3] arm64: dts: exynos: gs101: add CPU clocks Tudor Ambarus
2025-09-24 15:14 ` [PATCH v4 3/3] arm64: dts: exynos: gs101: add OPPs Tudor Ambarus
2025-10-20 7:06 ` [PATCH v4 0/3] arm64: dts: exynos: gs101: add cpufreq support Krzysztof Kozlowski
2025-10-20 7:07 ` 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=8b095395-8c09-45ba-8dcb-48cd81b8c0e0@kernel.org \
--to=krzk@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=andre.draszik@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel-team@android.com \
--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=peter.griffin@linaro.org \
--cc=robh@kernel.org \
--cc=tudor.ambarus@linaro.org \
--cc=will@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®