devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Cathy Xu (许华婷)" <ot_cathy.xu@mediatek.com>
To: "robh@kernel.org" <robh@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Lei Xue (薛磊)" <Lei.Xue@mediatek.com>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"Wenbin Mei (梅文彬)" <Wenbin.Mei@mediatek.com>,
	"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
	"Guodong Liu (刘国栋)" <Guodong.Liu@mediatek.com>,
	"Yong Mao (毛勇)" <yong.mao@mediatek.com>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"conor+dt@kernel.org" <conor+dt@kernel.org>,
	"sean.wang@kernel.org" <sean.wang@kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
	"Axe Yang (杨磊)" <Axe.Yang@mediatek.com>,
	"AngeloGioacchino Del Regno"
	<angelogioacchino.delregno@collabora.com>
Subject: Re: [PATCH v4 1/3] dt-bindings: pinctrl: mediatek: Add support for mt8196
Date: Fri, 28 Feb 2025 03:11:41 +0000	[thread overview]
Message-ID: <d5bf6e1b6c277e6431cffeef66a4766f59f94fe5.camel@mediatek.com> (raw)
In-Reply-To: <174070957527.867625.13463640154036333781.robh@kernel.org>

On Thu, 2025-02-27 at 20:26 -0600, Rob Herring (Arm) wrote:
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
> 
> 
> On Fri, 28 Feb 2025 09:16:25 +0800, Cathy Xu wrote:
> > Add the new binding document for pinctrl on MediaTek mt8196.
> > 
> > Signed-off-by: Guodong Liu <guodong.liu@mediatek.com>
> > Signed-off-by: Cathy Xu <ot_cathy.xu@mediatek.com>
> > ---
> >  .../pinctrl/mediatek,mt8196-pinctrl.yaml      | 241
> > ++++++++++++++++++
> >  1 file changed, 241 insertions(+)
> >  create mode 100644
> > Documentation/devicetree/bindings/pinctrl/mediatek,mt8196-
> > pinctrl.yaml
> > 
> 
> My bot found errors running 'make dt_binding_check' on your patch:

  Sorry, this patch depond on another patch:
  
https://patchwork.kernel.org/project/linux-mediatek/patch/20250228011702.16493-3-ot_cathy.xu@mediatek.com/
  In this case, does the dt-binding still need go first? If so, I 
will include the dependency information in the commit message of 
the next version. Thank you~

> 
> yamllint warnings/errors:
> 
> dtschema/dtc warnings/errors:
> Documentation/devicetree/bindings/pinctrl/mediatek,mt8196-
> pinctrl.example.dts:24:18: fatal error:
> ../../../../arch/arm64/boot/dts/mediatek/mt8196-pinfunc.h: No such
> file or directory
>    24 |         #include
> "../../../../arch/arm64/boot/dts/mediatek/mt8196-pinfunc.h"
>       |                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ~~~~~~~~~~~~~~~
> compilation terminated.
> make[2]: *** [scripts/Makefile.dtbs:131:
> Documentation/devicetree/bindings/pinctrl/mediatek,mt8196-
> pinctrl.example.dtb] Error 1
> make[2]: *** Waiting for unfinished jobs....
> make[1]: *** [/builds/robherring/dt-review-ci/linux/Makefile:1511:
> dt_binding_check] Error 2
> make: *** [Makefile:251: __sub-make] Error 2
> 
> doc reference errors (make refcheckdocs):
> 
> See 
> https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20250228011702.16493-2-ot_cathy.xu@mediatek.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.
> 

  reply	other threads:[~2025-02-28  3:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-28  1:16 [PATCH v4 0/3] pinctrl: mediatek: Add pinctrl driver on mt8196 Cathy Xu
2025-02-28  1:16 ` [PATCH v4 1/3] dt-bindings: pinctrl: mediatek: Add support for mt8196 Cathy Xu
2025-02-28  2:26   ` Rob Herring (Arm)
2025-02-28  3:11     ` Cathy Xu (许华婷) [this message]
2025-02-28  7:16       ` Krzysztof Kozlowski
2025-02-28  8:54         ` Cathy Xu (许华婷)
2025-02-28  1:16 ` [PATCH v4 2/3] arm64: dts: mediatek: mt8196: Add pinmux macro header file Cathy Xu
2025-02-28  1:16 ` [PATCH v4 3/3] pinctrl: mediatek: Add pinctrl driver on mt8196 Cathy Xu
2025-02-28  8:49   ` AngeloGioacchino Del Regno
2025-02-28  8:59     ` Cathy Xu (许华婷)
2025-02-28  9:12     ` Cathy Xu (许华婷)

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=d5bf6e1b6c277e6431cffeef66a4766f59f94fe5.camel@mediatek.com \
    --to=ot_cathy.xu@mediatek.com \
    --cc=Axe.Yang@mediatek.com \
    --cc=Guodong.Liu@mediatek.com \
    --cc=Lei.Xue@mediatek.com \
    --cc=Wenbin.Mei@mediatek.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=robh@kernel.org \
    --cc=sean.wang@kernel.org \
    --cc=yong.mao@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;
as well as URLs for NNTP newsgroup(s).