From: Wolfram Sang <wsa@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
devicetree@vger.kernel.org, "Ray Jui" <rjui@broadcom.com>,
"Rob Herring" <robh+dt@kernel.org>,
bcm-kernel-feedback-list@broadcom.com,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Rafał Miłecki" <rafal@milecki.pl>,
linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
"Scott Branden" <sbranden@broadcom.com>
Subject: Re: [PATCH] dt-bindings: i2c: brcm,iproc-i2c: convert to the json-schema
Date: Fri, 28 May 2021 11:23:06 +0200 [thread overview]
Message-ID: <YLC2en7Mj7kurlCd@kunai> (raw)
In-Reply-To: <1620844516.523024.204087.nullmailer@robh.at.kernel.org>
[-- Attachment #1: Type: text/plain, Size: 781 bytes --]
Hi Rob,
> 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:
> Documentation/devicetree/bindings/i2c/brcm,iproc-i2c.example.dt.yaml:0:0: /example-0/i2c@18008000/wm8750@1a: failed to match any schema with compatible: ['wlf,wm8750']
A generic question:
So sound/wm8750.txt was not converted yet. However, if this conversion
is fine otherwise, I'd vote to apply it nonetheless because it is one
conversion less to do then. Alternatively, we could change the example
to include a simple EEPROM which has an already converted binding doc.
What is the procedure here?
All the best and thanks for your work!
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-05-28 9:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 16:07 [PATCH] dt-bindings: i2c: brcm,iproc-i2c: convert to the json-schema Rafał Miłecki
2021-05-12 18:35 ` Rob Herring
2021-05-28 9:23 ` Wolfram Sang [this message]
2021-05-28 9:37 ` Rafał Miłecki
2021-05-28 9:57 ` Wolfram Sang
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=YLC2en7Mj7kurlCd@kunai \
--to=wsa@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=rafal@milecki.pl \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sbranden@broadcom.com \
--cc=zajec5@gmail.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).