From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Kathiravan T <quic_kathirav@quicinc.com>
Cc: Rob Herring <robh+dt@kernel.org>, Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
devicetree@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH V2 1/4] dt-bindings: nvmem: qfprom: add compatible for few IPQ SoCs
Date: Tue, 30 May 2023 15:03:09 +0200 [thread overview]
Message-ID: <8ea4e54a-56bc-c3a9-f67e-7d2fad4ba09c@linaro.org> (raw)
In-Reply-To: <20230530125918.4waqxc4xmnetb5wb@krzk-bin>
On 30/05/2023 14:59, Krzysztof Kozlowski wrote:
> On Fri, 26 May 2023 18:23:02 +0530, Kathiravan T wrote:
>> Add the QFPROM compatible for IPQ5332, IPQ6018 and IPQ9574
>>
>> Signed-off-by: Kathiravan T <quic_kathirav@quicinc.com>
>> ---
>> Changes in V2:
>> - No changes
>>
>> Documentation/devicetree/bindings/nvmem/qcom,qfprom.yaml | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>
> Running 'make dtbs_check' with the schema in this patch gives the
> following warnings. Consider if they are expected or the schema is
> incorrect. These may not be new warnings.
>
> Note that it is not yet a requirement to have 0 warnings for dtbs_check.
> This will change in the future.
>
> Full log is available here: https://patchwork.ozlabs.org/patch/1786533
>
>
> qfprom@1b44000: compatible:0: 'qcom,qcm2290-qfprom' is not one of ['qcom,apq8064-qfprom', 'qcom,apq8084-qfprom', 'qcom,ipq5332-qfprom', 'qcom,ipq6018-qfprom', 'qcom,ipq8064-qfprom', 'qcom,ipq8074-qfprom', 'qcom,ipq9574-qfprom', 'qcom,msm8916-qfprom', 'qcom,msm8974-qfprom', 'qcom,msm8976-qfprom', 'qcom,msm8996-qfprom', 'qcom,msm8998-qfprom', 'qcom,qcs404-qfprom', 'qcom,sc7180-qfprom', 'qcom,sc7280-qfprom', 'qcom,sdm630-qfprom', 'qcom,sdm670-qfprom', 'qcom,sdm845-qfprom', 'qcom,sm6115-qfprom', 'qcom,sm6350-qfprom', 'qcom,sm6375-qfprom', 'qcom,sm8150-qfprom', 'qcom,sm8250-qfprom']
> arch/arm64/boot/dts/qcom/qrb2210-rb1.dtb
Not related, can be ignored.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-05-30 13:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 12:53 [PATCH V2 0/4] Add QFPROM support " Kathiravan T
2023-05-26 12:53 ` [PATCH V2 1/4] dt-bindings: nvmem: qfprom: add compatible " Kathiravan T
2023-05-30 12:59 ` Krzysztof Kozlowski
2023-05-30 13:03 ` Krzysztof Kozlowski [this message]
2023-05-30 13:03 ` Krzysztof Kozlowski
2023-05-26 12:53 ` [PATCH V2 2/4] arm64: dts: qcom: ipq5332: add QFPROM node Kathiravan T
2023-05-26 12:53 ` [PATCH V2 3/4] arm64: dts: qcom: ipq6018: " Kathiravan T
2023-05-26 12:54 ` Konrad Dybcio
2023-05-26 13:22 ` Dmitry Baryshkov
2023-05-26 13:28 ` Konrad Dybcio
2023-05-26 12:53 ` [PATCH V2 4/4] arm64: dts: qcom: ipq9574: " Kathiravan T
2023-05-27 1:07 ` [PATCH V2 0/4] Add QFPROM support for few IPQ SoCs Bjorn Andersson
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=8ea4e54a-56bc-c3a9-f67e-7d2fad4ba09c@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_kathirav@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.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
all inboxes | Powered by JetHome®