[PATCH v3 2/3] dt-bindings: mfd: mediatek: mt6397: Convert to DT schema format

[Macpaul Lin]

On 9/14/24 03:23, Rob Herring (Arm) wrote:
> 	
> 
> External email : Please do not click links or open attachments until you 
> have verified the sender or the content.
> 
> On Sat, 14 Sep 2024 01:59:26 +0800, Macpaul Lin wrote:
>> Convert the mfd: mediatek: mt6397 binding to DT schema format.
>> 

[snip]

>> 
> 
> My bot found errors running 'make dt_binding_check' on your patch:
> 
> yamllint warnings/errors:
> 
> dtschema/dtc warnings/errors:
> Warning: Duplicate compatible "mediatek,mt6357" found in schemas matching "$id":

I'm using dtschema 2024.09 and the dt_bindings_check didn't report this 
issue even the full check has been run.
However, the compatible "mediatek,mt6357" indeed existed in the old 
bindings. Since it is a independent DT schema now, I'll remove this line
and update v4 version to see if it will help.

Is there new version of dtschema used by bot? I guess the base shouldn't 
affect this duplicate detection whether using rc-1 or next-20240906.

[snip]

> 
> doc reference errors (make refcheckdocs):
> 
> See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20240913175926.7443-1-macpaul.lin@mediatek.com
> 
> The base for the series is generally the latest rc1. A different dependency
> should be noted in *this* patch
The base of this patch set is based on next-20240906 with linux-next/master.

> 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.
> 

Thanks
Macpaul Lin