From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Alim Akhtar" <alim.akhtar@samsung.com>,
"Catalin Marinas" <catalin.marinas@arm.com>,
willmcvicker@google.com, kernel-team@android.com,
"Will Deacon" <will@kernel.org>,
"André Draszik" <andre.draszik@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Peter Griffin" <peter.griffin@linaro.org>
Subject: Re: [PATCH v3 0/3] arm64: dts: exynos: gs101: add cpufreq support
Date: Thu, 4 Sep 2025 15:28:18 +0100 [thread overview]
Message-ID: <3cc48a65-5d08-4469-9ed7-f836a2210702@linaro.org> (raw)
In-Reply-To: <175699523574.4060004.693479596122414416.robh@kernel.org>
On 9/4/25 3:17 PM, Rob Herring (Arm) wrote:
> arch/arm64/boot/dts/exynos/google/gs101.dtsi:10:10: fatal error: dt-bindings/clock/google,gs101-acpm.h: No such file or directory
> 10 | #include <dt-bindings/clock/google,gs101-acpm.h>
That's alright, I described in the cover letter the dependency on the patch
that adds this bindings file. Thanks!
ta
prev parent reply other threads:[~2025-09-04 14:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 14:24 [PATCH v3 0/3] arm64: dts: exynos: gs101: add cpufreq support Tudor Ambarus
2025-09-03 14:24 ` [PATCH v3 1/3] arm64: dts: exynos: gs101: add #clock-cells to the ACPM protocol node Tudor Ambarus
2025-09-03 14:24 ` [PATCH v3 2/3] arm64: dts: exynos: gs101: add CPU clocks Tudor Ambarus
2025-09-03 14:24 ` [PATCH v3 3/3] arm64: dts: exynos: gs101: add OPPs Tudor Ambarus
2025-09-04 14:17 ` [PATCH v3 0/3] arm64: dts: exynos: gs101: add cpufreq support Rob Herring (Arm)
2025-09-04 14:28 ` Tudor Ambarus [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=3cc48a65-5d08-4469-9ed7-f836a2210702@linaro.org \
--to=tudor.ambarus@linaro.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=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;
as well as URLs for NNTP newsgroup(s).