mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Lo <james.lo@mediatek.com>
To: Rob Herring <robh@kernel.org>
Cc: <linux-kernel@vger.kernel.org>,
	Hsin-Hsiung Wang <hsin-hsiung.wang@mediatek.com>,
	<Project_Global_Chrome_Upstream_Group@mediatek.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	<devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	Stephen Boyd <sboyd@kernel.org>,
	"Rob Herring" <robh+dt@kernel.org>, <srv_heupstream@mediatek.com>,
	<linux-mediatek@lists.infradead.org>
Subject: Re: [RESEND, v13 2/4] dt-bindings: spmi: document binding for the Mediatek SPMI controller
Date: Thu, 4 Nov 2021 17:52:36 +0800	[thread overview]
Message-ID: <4c3036d8181c788fbf047883e2f49172edbe3f0f.camel@mediatek.com> (raw)
In-Reply-To: <1635944770.215632.1040288.nullmailer@robh.at.kernel.org>

On Wed, 2021-11-03 at 08:06 -0500, Rob Herring wrote:
> On Wed, 03 Nov 2021 16:10:19 +0800, James Lo wrote:
> > This adds documentation for the SPMI controller found on Mediatek
> > SoCs.
> > 
> > Signed-off-by: Hsin-Hsiung Wang <hsin-hsiung.wang@mediatek.com>
> > ---
> >  .../bindings/spmi/mtk,spmi-mtk-pmif.yaml      | 76
> > +++++++++++++++++++
> >  1 file changed, 76 insertions(+)
> >  create mode 100644
> > Documentation/devicetree/bindings/spmi/mtk,spmi-mtk-pmif.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/linux-dt-
> review/Documentation/devicetree/bindings/spmi/mtk,spmi-mtk-
> pmif.example.dt.yaml: spmi@10027000: reg: [[268595200, 3584],
> [268603392, 256]] is too long
> 	From schema: /builds/robherring/linux-dt-
> review/Documentation/devicetree/bindings/spmi/mtk,spmi-mtk-pmif.yaml
> /builds/robherring/linux-dt-
> review/Documentation/devicetree/bindings/spmi/mtk,spmi-mtk-
> pmif.example.dt.yaml: spmi@10027000: reg: [[268595200, 3584],
> [268603392, 256]] is too long
> 	From schema: /builds/robherring/linux-dt-
> review/Documentation/devicetree/bindings/spmi/spmi.yaml
> 
> doc reference errors (make refcheckdocs):
> 
> See 
> https://urldefense.com/v3/__https://patchwork.ozlabs.org/patch/1550144__;!!CTRNKA9wMg0ARbw!yBdAIu8sF9FdGe9H9yO19pC0PvopKz_1DwYCmY0g5pqXvOC6acHZh_NfySMb2x_n$
>  
> 
> 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.
> 

Dear Rob,

Due to [RESEND,v13,2/4] depends on [RESEND,v13,1/4],
so we local can pass yaml when apply all 4 patches,
and fail only apply [RESEND,v13,2/4] as your bot's result.

Should we merge [RESEND,v13,2/4] and [RESEND,v13,2/4] to one patch ?
Or Could your bot help to run yaml check for all 4 patches applied (one
series) ?


Many thanks


  reply	other threads:[~2021-11-04  9:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-03  8:10 [RESEND, v13 0/4] Add SPMI support for Mediatek SoC IC James Lo
2021-11-03  8:10 ` [RESEND, v13 1/4] dt-bindings: spmi: modify the constraint of reg property James Lo
2021-11-03  8:10 ` [RESEND, v13 2/4] dt-bindings: spmi: document binding for the Mediatek SPMI controller James Lo
2021-11-03 13:06   ` Rob Herring
2021-11-04  9:52     ` James Lo [this message]
2021-11-04  1:06   ` Rob Herring
2021-11-03  8:10 ` [RESEND, v13 3/4] spmi: mediatek: Add support for MT6873/8192 James Lo
2021-11-03  8:10 ` [RESEND, v13 4/4] spmi: mediatek: Add support for MT8195 James Lo

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=4c3036d8181c788fbf047883e2f49172edbe3f0f.camel@mediatek.com \
    --to=james.lo@mediatek.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hsin-hsiung.wang@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=srv_heupstream@mediatek.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

Powered by JetHome