From: Lee Jones <lee.jones@linaro.org>
To: Benjamin GAIGNARD <benjamin.gaignard@st.com>
Cc: Fabio Estevam <festevam@gmail.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [RFC] dt-bindings: mfd: st,stmfx: Remove extra additionalProperties
Date: Wed, 1 Jul 2020 10:36:58 +0100 [thread overview]
Message-ID: <20200701093658.GY1179328@dell> (raw)
In-Reply-To: <18c2405c-3c9d-58e0-c5ab-61a214341322@st.com>
On Wed, 01 Jul 2020, Benjamin GAIGNARD wrote:
>
>
> On 6/29/20 9:23 PM, Fabio Estevam wrote:
> > The following build error is seen with 'make dt_binding_check':
> >
> > CHKDT Documentation/devicetree/bindings/mfd/st,stmfx.yaml
> > /home/fabio/linux-next/Documentation/devicetree/bindings/mfd/st,stmfx.yaml: properties:pinctrl:patternProperties: {'enum': ['$ref', 'additionalItems', 'additionalProperties', 'allOf', 'anyOf', 'const', 'contains', 'default', 'dependencies', 'deprecated', 'description', 'else', 'enum', 'if', 'items', 'maxItems', 'maximum', 'minItems', 'minimum', 'multipleOf', 'not', 'oneOf', 'pattern', 'patternProperties', 'properties', 'propertyNames', 'required', 'then', 'unevaluatedProperties']} is not allowed for 'additionalProperties'
> >
> > Remove the extra 'additionalProperties' to pass the build.
> Reviewed-by: Benjamin Gaignard <benjamin.gaignard@st.com>
FYI: The resend of this patch has already been applied.
--
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2020-07-01 9:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 19:23 [RFC] dt-bindings: mfd: st,stmfx: Remove extra additionalProperties Fabio Estevam
2020-06-30 2:02 ` Rob Herring
2020-06-30 7:08 ` Lee Jones
2020-07-01 7:21 ` Benjamin GAIGNARD
2020-07-01 9:36 ` Lee Jones [this message]
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=20200701093658.GY1179328@dell \
--to=lee.jones@linaro.org \
--cc=benjamin.gaignard@st.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.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;
as well as URLs for NNTP newsgroup(s).