From: Gopikishan Thawre <gopikishan.thawre@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Abel Vesa <abelvesa@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Richard Cochran <richardcochran@gmail.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: arm: qcom: Add LeMans Draco EVK board
Date: Tue, 27 Oct 2026 12:29:43 +0530 [thread overview]
Message-ID: <8ec30a0f-2c9d-4011-8e26-9ec51c68681d@oss.qualcomm.com> (raw)
In-Reply-To: <20261020-accelerated-husky-of-whirlwind-ce022c@quoll>
Hi Krzysztof Kozlowski,
On 10/20/2026 1:21 PM, Krzysztof Kozlowski wrote:
> On Mon, Oct 19, 2026 at 03:57:32PM +0530, Gopikishan Thawre wrote:
>> Add the qcom,lemans-draco-evk compatible string for the LeMans Draco EVK
>> board, which pairs the LeMans Draco EVK SoM with a common carrier board.
>
> So here you explain any oddities, like why SoM has no dedicated
> compatible and why common carrier board means it is not common but
> SoM specific.
>
Thanks for review and suggestions.
Agreed. The LeMans Draco SoM is the module itself, while the complete
SoM and Draco carrier board combination is the LeMans Draco EVK. I will
update the commit message accordingly in v2.
Best Regards,
Gopikishan
next prev parent reply other threads:[~2026-10-27 6:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 10:27 [PATCH 0/3] Add support for LeMans Draco EVK board Gopikishan Thawre
2026-10-19 10:27 ` [PATCH 1/3] dt-bindings: arm: qcom: Add " Gopikishan Thawre
2026-10-20 7:51 ` Krzysztof Kozlowski
2026-10-27 6:59 ` Gopikishan Thawre [this message]
2026-10-19 10:27 ` [PATCH 2/3] arm64: dts: qcom: lemans: Add Draco EVK SoM platform Gopikishan Thawre
2026-10-19 10:27 ` [PATCH 3/3] arm64: dts: qcom: lemans: Add Draco EVK board Gopikishan Thawre
2026-10-19 12:05 ` Dmitry Baryshkov
2026-10-27 8:28 ` Gopikishan Thawre
2026-10-19 12:31 ` Konrad Dybcio
2026-10-27 8:23 ` Gopikishan Thawre
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=8ec30a0f-2c9d-4011-8e26-9ec51c68681d@oss.qualcomm.com \
--to=gopikishan.thawre@oss.qualcomm.com \
--cc=abelvesa@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=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=robh@kernel.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