From: Krzysztof Kozlowski <krzk@kernel.org>
To: Yuvaraj Ranganathan <quic_yrangana@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@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
Subject: Re: [PATCH 1/2] arm64: dts: qcom: sa8775p: add QCrypto node
Date: Fri, 28 Mar 2025 10:09:59 +0100 [thread overview]
Message-ID: <aaf21b5e-e910-4e03-b9a9-f37b7dd118bb@kernel.org> (raw)
In-Reply-To: <6ccf4cad-a99b-4168-b4d7-577112c011e1@quicinc.com>
On 28/03/2025 09:32, Yuvaraj Ranganathan wrote:
>
>
> On 3/28/2025 12:47 PM, Krzysztof Kozlowski wrote:
>> On 28/03/2025 07:04, Yuvaraj Ranganathan wrote:
>>>>>> Use commit SHA syntax (see submitting patches, checkpatch).
>>>>>>
>>>>>>> because of the build warning,
>>>>>>>
>>>>>>> sa8775p-ride.dtb: crypto@1dfa000: compatible: 'oneOf' conditional failed, one must be fixed:
>>>>>>> ...
>>>>>>> 'qcom,sa8775p-qce' is not one of ['qcom,ipq4019-qce', 'qcom,sm8150-qce']
>>>>>>
>>>>>> Not relevant warning.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Best regards,
>>>>>> Krzysztof
>>>>>
>>>>> Are you saying this is not the warning seen at merging?
>>>> Tell me how it is relevant? Tell me how can I reproduce it.
>>>>
>>>> Best regards,
>>>> Krzysztof
>>>
>>> Below commands will show the above warnings without the fix,
>>> make clean && make qcom/qcs9100-ride.dtb CHECK_DTBS=1
>>> make clean && make qcom/qcs8300-ride.dtb CHECK_DTBS=1
>>
>> As I suspected, not possible to reproduce.
>>
>> Best regards,
>> Krzysztof
>
> I'm able to reproduce without this fix, I hope you are discussing about
> this failure only,
>
> from schema $id:
> http://devicetree.org/schemas/net/bluetooth/qualcomm-bluetooth.yaml#
I suspect you work on outdated tree. I followed your instructions on my
tree (you did not specify which) and did not see these errors.
I bet you reply now third time, without any more details claiming the
same but it's just waste of my time.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-28 9:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 18:08 [PATCH 1/2] arm64: dts: qcom: sa8775p: add QCrypto node Yuvaraj Ranganathan
2025-02-27 18:08 ` [PATCH 2/2] arm64: dts: qcom: qcs8300: " Yuvaraj Ranganathan
2025-02-28 0:28 ` Bjorn Andersson
2025-03-01 16:59 ` Dmitry Baryshkov
2025-02-28 0:26 ` [PATCH 1/2] arm64: dts: qcom: sa8775p: " Bjorn Andersson
2025-02-28 5:31 ` Yuvaraj Ranganathan
2025-02-28 14:14 ` Bjorn Andersson
2025-03-01 13:36 ` Krzysztof Kozlowski
2025-03-25 5:20 ` Yuvaraj Ranganathan
2025-03-25 7:30 ` Krzysztof Kozlowski
2025-03-26 17:40 ` Yuvaraj Ranganathan
2025-03-27 7:08 ` Krzysztof Kozlowski
2025-03-28 6:04 ` Yuvaraj Ranganathan
2025-03-28 7:17 ` Krzysztof Kozlowski
2025-03-28 8:32 ` Yuvaraj Ranganathan
2025-03-28 9:09 ` Krzysztof Kozlowski [this message]
2025-03-28 12:48 ` Dmitry Baryshkov
2025-03-29 12:08 ` Konrad Dybcio
2025-03-26 17:34 ` Dmitry Baryshkov
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=aaf21b5e-e910-4e03-b9a9-f37b7dd118bb@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=quic_yrangana@quicinc.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