From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: "Peter Griffin" <peter.griffin@linaro.org>,
"Alim Akhtar" <alim.akhtar@samsung.com>,
"Conor Dooley" <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
"Will Deacon" <will@kernel.org>,
willmcvicker@google.com, linux-kernel@vger.kernel.org,
linux-samsung-soc@vger.kernel.org,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Catalin Marinas" <catalin.marinas@arm.com>,
kernel-team@android.com, devicetree@vger.kernel.org,
"André Draszik" <andre.draszik@linaro.org>
Subject: Re: [PATCH v2 0/3] arm64: dts: exynos: gs101: add cpufreq support
Date: Thu, 28 Aug 2025 06:30:56 +0100 [thread overview]
Message-ID: <05e9dfa9-d628-4a4d-8cc3-f6854cc186d9@linaro.org> (raw)
In-Reply-To: <175633665113.3746832.15304875656374701987.robh@kernel.org>
On 8/28/25 12:18 AM, Rob Herring (Arm) wrote:
> New warnings running 'make CHECK_DTBS=y for arch/arm64/boot/dts/exynos/' for 20250827-acpm-dvfs-dt-v2-0-e1d2890d12b4@linaro.org:
>
> Error: arch/arm64/boot/dts/exynos/google/gs101.dtsi:75.24-25 syntax error
> FATAL ERROR: Unable to parse input tree
That's alright. There's a dependency on a bindings patch that's described in
the cover letter.
prev parent reply other threads:[~2025-08-28 5:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 12:59 [PATCH v2 0/3] arm64: dts: exynos: gs101: add cpufreq support Tudor Ambarus
2025-08-27 12:59 ` [PATCH v2 1/3] arm64: dts: exynos: gs101: add #clock-cells to the ACPM protocol node Tudor Ambarus
2025-08-27 12:59 ` [PATCH v2 2/3] arm64: dts: exynos: gs101: add CPU clocks Tudor Ambarus
2025-08-27 12:59 ` [PATCH v2 3/3] arm64: dts: exynos: gs101: add OPPs Tudor Ambarus
2025-08-27 23:18 ` [PATCH v2 0/3] arm64: dts: exynos: gs101: add cpufreq support Rob Herring (Arm)
2025-08-28 5:30 ` 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=05e9dfa9-d628-4a4d-8cc3-f6854cc186d9@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).