From: Rob Herring <robh@kernel.org>
To: Dongchun Zhu <dongchun.zhu@mediatek.com>
Cc: robh+dt@kernel.org, linux-media@vger.kernel.org,
mark.rutland@arm.com, shengnan.wang@mediatek.com,
linux-mediatek@lists.infradead.org,
andriy.shevchenko@linux.intel.com, matthias.bgg@gmail.com,
devicetree@vger.kernel.org, sj.huang@mediatek.com,
sakari.ailus@linux.intel.com, louis.kuo@mediatek.com,
drinkcat@chromium.org, tfiga@chromium.org,
srv_heupstream@mediatek.com, mchehab@kernel.org,
linux-arm-kernel@lists.infradead.org, bingbu.cao@intel.com
Subject: Re: [PATCH v14 1/2] media: dt-bindings: media: i2c: Document OV02A10 bindings
Date: Thu, 3 Sep 2020 10:13:46 -0600 [thread overview]
Message-ID: <20200903161346.GA2875415@bogus> (raw)
In-Reply-To: <20200902120122.24456-2-dongchun.zhu@mediatek.com>
On Wed, 02 Sep 2020 20:01:21 +0800, Dongchun Zhu wrote:
> Add YAML device tree binding for OV02A10 CMOS image sensor,
> and the relevant MAINTAINERS entries.
>
> Signed-off-by: Dongchun Zhu <dongchun.zhu@mediatek.com>
> ---
> .../bindings/media/i2c/ovti,ov02a10.yaml | 161 +++++++++++++++++++++
> MAINTAINERS | 7 +
> 2 files changed, 168 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/media/i2c/ovti,ov02a10.yaml
>
My bot found errors running 'make dt_binding_check' on your patch:
Error: Documentation/devicetree/bindings/media/i2c/ovti,ov02a10.example.dts:28.45-46 syntax error
FATAL ERROR: Unable to parse input tree
make[1]: *** [scripts/Makefile.lib:342: Documentation/devicetree/bindings/media/i2c/ovti,ov02a10.example.dt.yaml] Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:1366: dt_binding_check] Error 2
See https://patchwork.ozlabs.org/patch/1355723
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-09-03 16:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 12:01 [PATCH v14 0/2] media: i2c: Add support for OV02A10 sensor Dongchun Zhu
2020-09-02 12:01 ` [PATCH v14 1/2] media: dt-bindings: media: i2c: Document OV02A10 bindings Dongchun Zhu
2020-09-03 16:13 ` Rob Herring [this message]
2020-09-04 3:24 ` Dongchun Zhu
2020-09-02 12:01 ` [PATCH v14 2/2] media: i2c: Add OV02A10 image sensor driver Dongchun Zhu
2020-09-02 13:44 ` Andy Shevchenko
2020-09-02 13:51 ` Andy Shevchenko
2020-09-04 13:32 ` Dongchun Zhu
2020-09-04 13:55 ` Andy Shevchenko
2020-09-08 9:46 ` Sakari Ailus
2020-09-04 13:22 ` Dongchun Zhu
2020-09-04 14:05 ` Andy Shevchenko
2020-09-07 13:15 ` Tomasz Figa
2020-09-07 13:51 ` Andy Shevchenko
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=20200903161346.GA2875415@bogus \
--to=robh@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bingbu.cao@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dongchun.zhu@mediatek.com \
--cc=drinkcat@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=louis.kuo@mediatek.com \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=shengnan.wang@mediatek.com \
--cc=sj.huang@mediatek.com \
--cc=srv_heupstream@mediatek.com \
--cc=tfiga@chromium.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).