From: Rob Herring <robh+dt@kernel.org>
To: Maxime Ripard <maxime.ripard@bootlin.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Wolfram Sang <wsa@the-dreams.de>,
Gregory Clement <gregory.clement@bootlin.com>,
Chen-Yu Tsai <wens@csie.org>,
Linux I2C <linux-i2c@vger.kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 2/2] dt-bindings: i2c: mv64xxx: Add YAML schemas
Date: Tue, 11 Jun 2019 09:33:42 -0600 [thread overview]
Message-ID: <CAL_JsqLXFaDsfrzBc6dUwsuBrhWs=w2m-pXjFBdQ_sm685kf2Q@mail.gmail.com> (raw)
In-Reply-To: <20190611090309.7930-2-maxime.ripard@bootlin.com>
On Tue, Jun 11, 2019 at 3:03 AM Maxime Ripard <maxime.ripard@bootlin.com> wrote:
>
> Switch the DT binding to a YAML schema to enable the DT validation.
>
> Signed-off-by: Maxime Ripard <maxime.ripard@bootlin.com>
>
> ---
>
> Changes from v2:
> - Remove the copy/pasted example and use the one we had before
>
> Changes from v1:
> - Fix the maintainers
> ---
> .../devicetree/bindings/i2c/i2c-mv64xxx.txt | 64 ---------
> .../bindings/i2c/marvell,mv64xxx-i2c.yaml | 124 ++++++++++++++++++
> 2 files changed, 124 insertions(+), 64 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/i2c/i2c-mv64xxx.txt
> create mode 100644 Documentation/devicetree/bindings/i2c/marvell,mv64xxx-i2c.yaml
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-06-11 15:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 9:03 [PATCH v3 1/2] dt-bindings: i2c: sun6i-p2wi: Add YAML schemas Maxime Ripard
2019-06-11 9:03 ` [PATCH v3 2/2] dt-bindings: i2c: mv64xxx: " Maxime Ripard
2019-06-11 15:33 ` Rob Herring [this message]
2019-06-25 9:57 ` Maxime Ripard
2019-06-25 10:03 ` Gregory CLEMENT
2019-06-26 13:31 ` Wolfram Sang
2019-06-11 15:34 ` [PATCH v3 1/2] dt-bindings: i2c: sun6i-p2wi: " Rob Herring
2019-06-26 13:31 ` 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='CAL_JsqLXFaDsfrzBc6dUwsuBrhWs=w2m-pXjFBdQ_sm685kf2Q@mail.gmail.com' \
--to=robh+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=gregory.clement@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@bootlin.com \
--cc=wens@csie.org \
--cc=wsa@the-dreams.de \
/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).