[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8636b916-749e-2bf7-8ec6-202aff4ab872@quicinc.com>
Date: Thu, 10 Aug 2023 15:57:20 +0530
From: Komal Bajaj <quic_kbajaj@...cinc.com>
To: Rob Herring <robh@...nel.org>
CC: <agross@...nel.org>, <devicetree@...r.kernel.org>,
<linux-arm-msm@...r.kernel.org>,
<krzysztof.kozlowski+dt@...aro.org>, <conor+dt@...nel.org>,
<linux-kernel@...r.kernel.org>, <konrad.dybcio@...aro.org>,
<srinivas.kandagatla@...aro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
<robh+dt@...nel.org>, <andersson@...nel.org>
Subject: Re: [PATCH 1/6] dt-bindings: cache: qcom,llcc: Add LLCC compatible
for QDU1000/QRU1000
On 8/10/2023 12:50 PM, Rob Herring wrote:
> On Thu, 10 Aug 2023 11:41:35 +0530, Komal Bajaj wrote:
>> Add LLCC compatible for QDU1000/QRU1000 SoCs and add optional
>> nvmem-cells and nvmem-cell-names properties to support multiple
>> configurations for multi channel DDR.
>>
>> Signed-off-by: Komal Bajaj <quic_kbajaj@...cinc.com>
>> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
>> ---
>> Documentation/devicetree/bindings/cache/qcom,llcc.yaml | 10 ++++++++++
>> 1 file changed, 10 insertions(+)
>>
> My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check'
> on your patch (DT_CHECKER_FLAGS is new in v5.13):
>
> yamllint warnings/errors:
>
> dtschema/dtc warnings/errors:
>
>
> doc reference errors (make refcheckdocs):
>
> See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20230810061140.15608-2-quic_kbajaj@quicinc.com
>
> The base for the series is generally the latest rc1. A different dependency
> should be noted in *this* patch.
>
> If you already ran 'make dt_binding_check' and didn't see the above
> error(s), then make sure 'yamllint' is installed and dt-schema is up to
> date:
>
> pip3 install dtschema --upgrade
>
> Please check and re-submit after running the above command yourself. Note
> that DT_SCHEMA_FILES can be set to your schema file to speed up checking
> your schema. However, it must be unset to test all examples with your schema.
Hi Rob,
I did run the same steps locally after upgrading dtschema too, but it
didn't reported any kind of error.
Here also, error is not mentioned, can you please state what's the error
reported with this patch?
Thanks
Komal
>
Powered by blists - more mailing lists