public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Sibi Sankar <quic_sibis@quicinc.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	robh+dt@kernel.org, linux-arm-msm@vger.kernel.org,
	andersson@kernel.org, manivannan.sadhasivam@linaro.org,
	konrad.dybcio@somainline.org, krzysztof.kozlowski+dt@linaro.org,
	jassisinghbrar@gmail.com, agross@kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: mailbox: Add dt binding for QTI CPUCP mailbox controller
Date: Wed, 14 Sep 2022 06:08:03 -0500	[thread overview]
Message-ID: <1663153683.714744.1742263.nullmailer@robh.at.kernel.org> (raw)
In-Reply-To: <1663135386-26270-2-git-send-email-quic_sibis@quicinc.com>

On Wed, 14 Sep 2022 11:33:05 +0530, Sibi Sankar wrote:
> Add devicetree binding for CPUSS Control Processor (CPUCP) mailbox
> controller.
> 
> Signed-off-by: Sibi Sankar <quic_sibis@quicinc.com>
> ---
>  .../bindings/mailbox/qcom,cpucp-mbox.yaml          | 51 ++++++++++++++++++++++
>  1 file changed, 51 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/mailbox/qcom,cpucp-mbox.yaml
> 

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:
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/mailbox/qcom,cpucp-mbox.example.dtb: mailbox@17400000: reg: [[0, 398458880], [0, 16], [0, 408486656], [0, 1792]] is too long
	From schema: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/mailbox/qcom,cpucp-mbox.yaml

doc reference errors (make refcheckdocs):

See https://patchwork.ozlabs.org/patch/

This check can fail if there are any dependencies. The base for a patch
series is generally the most recent rc1.

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.


  reply	other threads:[~2022-09-14 11:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-14  6:03 [PATCH 0/2] Add support for CPUCP mailbox controller Sibi Sankar
2022-09-14  6:03 ` [PATCH 1/2] dt-bindings: mailbox: Add dt binding for QTI " Sibi Sankar
2022-09-14 11:08   ` Rob Herring [this message]
2022-09-15  1:39     ` Sibi Sankar
2022-09-14  6:03 ` [PATCH 2/2] mailbox: Add support " Sibi Sankar
2022-09-14 17:38   ` Trilok Soni
2022-09-15  1:33     ` Sibi Sankar
2022-09-14 17:52   ` Bjorn Andersson
2022-11-03 11:02   ` Sudeep Holla
  -- strict thread matches above, loose matches on Subject: below --
2022-12-13 14:04 [PATCH 0/2] Add support for " Sibi Sankar
2022-12-13 14:04 ` [PATCH 1/2] dt-bindings: mailbox: Add dt binding for QTI " Sibi Sankar
2022-12-13 14:09   ` Sibi Sankar
2022-12-13 16:51   ` Rob Herring

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=1663153683.714744.1742263.nullmailer@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jassisinghbrar@gmail.com \
    --cc=konrad.dybcio@somainline.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=quic_sibis@quicinc.com \
    --cc=robh+dt@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