From: Rob Herring <robh@kernel.org>
To: Jeff Chase <jnchase@google.com>
Cc: robh+dt@kernel.org, hverkuil-cisco@xs4all.nl, mchehab@kernel.org,
devicetree@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: Add ch7322 media i2c device
Date: Mon, 18 May 2020 08:15:44 -0600 [thread overview]
Message-ID: <20200518141544.GA31928@bogus> (raw)
In-Reply-To: <20200515025159.101081-2-jnchase@google.com>
On Thu, 14 May 2020 22:51:58 -0400, Jeff Chase wrote:
> The ch7322 is a Chrontel CEC controller.
>
> Signed-off-by: Jeff Chase <jnchase@google.com>
> ---
> .../bindings/media/i2c/chrontel,ch7322.yaml | 65 +++++++++++++++++++
> .../devicetree/bindings/vendor-prefixes.yaml | 2 +
> MAINTAINERS | 7 ++
> 3 files changed, 74 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/media/i2c/chrontel,ch7322.yaml
>
My bot found errors running 'make dt_binding_check' on your patch:
Documentation/devicetree/bindings/media/i2c/chrontel,ch7322.yaml: $id: relative path/filename doesn't match actual path or filename
expected: http://devicetree.org/schemas/media/i2c/chrontel,ch7322.yaml#
See https://patchwork.ozlabs.org/patch/1290799
If you already ran 'make dt_binding_check' and didn't see the above
error(s), then make sure dt-schema is up to date:
pip3 install git+https://github.com/devicetree-org/dt-schema.git@master --upgrade
Please check and re-submit.
next prev parent reply other threads:[~2020-05-18 14:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 2:51 [PATCH v2 0/2] CH7322 CEC controller driver Jeff Chase
2020-05-15 2:51 ` [PATCH v2 1/2] dt-bindings: Add ch7322 media i2c device Jeff Chase
2020-05-18 14:15 ` Rob Herring [this message]
2020-05-15 2:51 ` [PATCH v2 2/2] media: cec: i2c: ch7322: Add ch7322 CEC controller driver Jeff Chase
2020-05-18 9:34 ` Hans Verkuil
2020-05-28 22:55 ` Jeff Chase
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=20200518141544.GA31928@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jnchase@google.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--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).