From: Rob Herring <robh@kernel.org>
To: Saravanan Sekar <sravanhome@gmail.com>
Cc: lee.jones@linaro.org, andy.shevchenko@gmail.com,
robh+dt@kernel.org, jic23@kernel.org, knaack.h@gmx.de,
lars@metafoo.de, pmeerw@pmeerw.net, sre@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-iio@vger.kernel.org, linux-pm@vger.kernel.org,
Saravanan Sekar <sravanhome@gmail.com>
Subject: Re: [PATCH v9 1/6] dt-bindings: mfd: add document bindings for mp2629
Date: Thu, 16 Apr 2020 15:44:34 -0500 [thread overview]
Message-ID: <20200416204434.GA17165@bogus> (raw)
In-Reply-To: <20200415162030.16414-2-sravanhome@gmail.com>
On Wed, 15 Apr 2020 18:20:25 +0200, Saravanan Sekar wrote:
> Add device tree binding information for mp2629 mfd driver.
>
> Signed-off-by: Saravanan Sekar <sravanhome@gmail.com>
> ---
> .../devicetree/bindings/mfd/mps,mp2629.yaml | 60 +++++++++++++++++++
> 1 file changed, 60 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mfd/mps,mp2629.yaml
>
My bot found errors running 'make dt_binding_check' on your patch:
Documentation/devicetree/bindings/mfd/mps,mp2629.example.dts:19.22-32.11: Warning (unit_address_vs_reg): /example-0/i2c@7e205000: node has a unit name, but no reg or ranges property
See https://patchwork.ozlabs.org/patch/1271317
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-04-16 20:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 16:20 [PATCH v9 0/6] Add battery charger driver support for MP2629 Saravanan Sekar
2020-04-15 16:20 ` [PATCH v9 1/6] dt-bindings: mfd: add document bindings for mp2629 Saravanan Sekar
2020-04-15 19:07 ` Peter Meerwald-Stadler
2020-04-16 20:44 ` Rob Herring [this message]
2020-04-15 16:20 ` [PATCH v9 2/6] mfd: mp2629: Add support for mps battery charger Saravanan Sekar
2020-04-24 7:18 ` Lee Jones
2020-04-24 7:26 ` saravanan sekar
2020-04-24 9:37 ` Lee Jones
2020-04-24 10:23 ` saravanan sekar
2020-04-24 10:53 ` Lee Jones
2020-04-24 11:04 ` saravanan sekar
2020-04-27 8:51 ` Lee Jones
2020-04-27 9:30 ` saravanan sekar
2020-04-30 10:39 ` saravanan sekar
2020-04-30 11:07 ` Andy Shevchenko
2020-04-27 7:26 ` Lee Jones
2020-04-15 16:20 ` [PATCH v9 3/6] iio: adc: mp2629: Add support for mp2629 ADC driver Saravanan Sekar
2020-04-15 16:20 ` [PATCH v9 4/6] power: supply: Add support for mps mp2629 battery charger Saravanan Sekar
2020-04-15 19:32 ` Peter Meerwald-Stadler
2020-04-15 16:20 ` [PATCH v9 5/6] power: supply: mp2629: Add impedance compenstation config Saravanan Sekar
2020-04-15 19:33 ` Peter Meerwald-Stadler
2020-04-15 16:20 ` [PATCH v9 6/6] MAINTAINERS: Add entry for mp2629 Battery Charger driver Saravanan Sekar
2020-04-15 16:40 ` [PATCH v9 0/6] Add battery charger driver support for MP2629 Andy Shevchenko
2020-04-15 16:53 ` saravanan sekar
2020-04-15 17:05 ` 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=20200416204434.GA17165@bogus \
--to=robh@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=lee.jones@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=sravanhome@gmail.com \
--cc=sre@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).