Re: [net-next RFC PATCH v2 3/4] dt-bindings: net: Document QCA808x PHYs

[Christian Marangi <ansuelsmth@gmail.com>]

On Mon, Dec 11, 2023 at 02:42:08PM -0600, Rob Herring wrote:
> 
> On Mon, 11 Dec 2023 20:23:17 +0100, Christian Marangi wrote:
> > Add Documentation for QCA808x PHYs for the additional LED configuration
> > for this PHY.
> > 
> > Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
> > ---
> > Changes v2:
> > - Fix License warning from checkpatch
> > - Drop redundant Description phrase
> > - Improve commit tile
> > - Drop special property (generalized)
> > 
> >  .../devicetree/bindings/net/qca,qca808x.yaml  | 58 +++++++++++++++++++
> >  1 file changed, 58 insertions(+)
> >  create mode 100644 Documentation/devicetree/bindings/net/qca,qca808x.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/net/qca,qca808x.yaml: 'anyOf' conditional failed, one must be fixed:
> 	'properties' is a required property
> 	'patternProperties' is a required property
> 	hint: Metaschema for devicetree binding documentation
> 	from schema $id: http://devicetree.org/meta-schemas/core.yaml#
> 
> doc reference errors (make refcheckdocs):
> 
> See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20231211192318.16450-3-ansuelsmth@gmail.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.
>

Erm sorry for the bot error... But How to handle this? 

-- 
	Ansuel