From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sudarshan Shetty <tessolveupstream@gmail.com>, andersson@kernel.org
Cc: konradybcio@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] arm64: dts: qcom: Add support for QCS615 talos evk board
Date: Fri, 17 Oct 2025 15:21:42 +0200 [thread overview]
Message-ID: <89f812bc-68ec-4a88-ac58-1f6797496151@kernel.org> (raw)
In-Reply-To: <20251014120223.1914790-3-tessolveupstream@gmail.com>
On 14/10/2025 14:02, Sudarshan Shetty wrote:
> Introduce the device tree support for the QCS615-based talos-evk
> platform, which follows the SMARC (Smart Mobility ARChitecture)
> standard. The platform is composed of two main hardware
> components: the talos-evk-som and the talos-evk carrier board.
>
> The talos-evk-som is a compact System on Module that integrates the
> QCS615 SoC, PMIC, and essential GPIO connectivity. It follows the
> SMARC standard, which defines a modular form factor allowing the SoM
> to be paired with different carrier boards for varied applications.
You already sent next patch so this is simply incomplete. Please squash
other work here.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-10-17 13:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 12:02 [PATCH v3 0/2] arm64: dts: qcom: Add support for QCS615 Talos EVK platform Sudarshan Shetty
2025-10-14 12:02 ` [PATCH v3 1/2] dt-bindings: arm: qcom: Add QCS615 Talos EVK SMARC platform Sudarshan Shetty
2025-10-17 5:13 ` Krzysztof Kozlowski
2025-10-22 9:58 ` Tessolve Upstream
2025-10-14 12:02 ` [PATCH v3 2/2] arm64: dts: qcom: Add support for QCS615 talos evk board Sudarshan Shetty
2025-10-14 22:15 ` Dmitry Baryshkov
2025-10-16 12:19 ` Tessolve Upstream
2025-10-17 13:21 ` Krzysztof Kozlowski [this message]
2025-10-22 9:57 ` Tessolve Upstream
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=89f812bc-68ec-4a88-ac58-1f6797496151@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tessolveupstream@gmail.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