From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ruchira Revdekar <ruchira.revdekar@oss.qualcomm.com>,
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>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Avaneesh Kumar Dwivedi <avaneesh.dwivedi@oss.qualcomm.com>,
Nirmesh Kumar Singh <nirmesh.singh@oss.qualcomm.com>
Subject: Re: [PATCH v2 1/4] dt-bindings: arm: qcom: Add Talos Lyra EVK board
Date: Tue, 13 Oct 2026 11:34:03 +0200 [thread overview]
Message-ID: <ca132d7b-a0d5-44f2-8b98-24570a88c9ce@kernel.org> (raw)
In-Reply-To: <2c93f85d-a6f0-420a-9b7d-cd72a7963ab8@oss.qualcomm.com>
On 13/10/2026 11:32, Ruchira Revdekar wrote:
> Hi Krzysztof,
>
> On 12-10-2026 16:54, Krzysztof Kozlowski wrote:
>> On 12/10/2026 08:16, Ruchira Revdekar wrote:
>>> From: Avaneesh Kumar Dwivedi <avaneesh.dwivedi@oss.qualcomm.com>
>>>
>>> Add the qcom,talos-lyra-evk compatible string for the Talos Lyra EVK
>>> board, which pairs the Talos Lyra EVK SoM with a common carrier board.
>>>
>>> Tested-by: Nirmesh Kumar Singh <nirmesh.singh@oss.qualcomm.com>
>>
>> No, this did not happen.
>>
>> Please do not add inapplicable/fake tags.
>>
>>
>> Best regards,
>> Krzysztof
>
> Apologies. The tag was added based on internal validation but Nirmesh
> had not yet formally posted it to the mailing list at the time of
> submission. That was a mistake on our part.
>
> Nirmesh has since replied to this thread with his formal Tested-by:
>
> Tested-by: Nirmesh Kumar Singh <nirmesh.singh@oss.qualcomm.com>
>
> will include it correctly in v3. The same applies to the identical
> tag in patch 2.
Again, this did not happen, otherwise explain me how did you execute
this code on the device during your "formal validation".
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-10-13 9:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 6:16 [PATCH v2 0/4] Add support for Talos Lyra EVK board Ruchira Revdekar
2026-10-12 6:16 ` [PATCH v2 1/4] dt-bindings: arm: qcom: Add " Ruchira Revdekar
2026-10-12 11:24 ` Krzysztof Kozlowski
2026-10-13 9:32 ` Ruchira Revdekar
2026-10-13 9:34 ` Krzysztof Kozlowski [this message]
2026-10-12 6:16 ` [PATCH v2 2/4] arm64: dts: qcom: talos: Add Talos Lyra EVK SoM platform Ruchira Revdekar
2026-10-12 6:27 ` sashiko-bot
2026-10-12 11:25 ` Krzysztof Kozlowski
2026-10-12 12:01 ` Dmitry Baryshkov
2026-10-12 6:16 ` [PATCH v2 3/4] arm64: dts: qcom: talos: Add Talos Lyra EVK board Ruchira Revdekar
2026-10-12 11:59 ` Dmitry Baryshkov
2026-10-12 12:02 ` Dmitry Baryshkov
2026-10-12 6:16 ` [PATCH v2 4/4] arm64: dts: qcom: talos: Add EL2 overlay for talos-lyra-evk Ruchira Revdekar
2026-10-12 11:26 ` Krzysztof Kozlowski
2026-10-12 15:34 ` Ruchira Revdekar
2026-10-13 8:55 ` [PATCH v2 0/4] Add support for Talos Lyra EVK board Nirmesh Kumar Singh
2026-10-13 9:34 ` Krzysztof Kozlowski
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=ca132d7b-a0d5-44f2-8b98-24570a88c9ce@kernel.org \
--to=krzk@kernel.org \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=avaneesh.dwivedi@oss.qualcomm.com \
--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=nirmesh.singh@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=ruchira.revdekar@oss.qualcomm.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