From: Rob Herring <robh@kernel.org>
To: Johan Jonker <jbx6244@gmail.com>
Cc: jic23@kernel.org, knaack.h@gmx.de, lars@metafoo.de,
pmeerw@pmeerw.net, heiko@sntech.de, robh+dt@kernel.org,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/3] dt-bindings: iio: adc: convert rockchip saradc bindings to yaml
Date: Mon, 30 Mar 2020 12:10:52 -0600 [thread overview]
Message-ID: <20200330181052.GA7527@bogus> (raw)
In-Reply-To: <20200313132926.10543-1-jbx6244@gmail.com>
On Fri, 13 Mar 2020 14:29:24 +0100, Johan Jonker wrote:
> Current dts files with 'saradc' nodes are manually verified.
> In order to automate this process rockchip-saradc.txt
> has to be converted to yaml.
>
> Signed-off-by: Johan Jonker <jbx6244@gmail.com>
> ---
> .../bindings/iio/adc/rockchip-saradc.txt | 37 ----------
> .../bindings/iio/adc/rockchip-saradc.yaml | 79 ++++++++++++++++++++++
> 2 files changed, 79 insertions(+), 37 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/iio/adc/rockchip-saradc.txt
> create mode 100644 Documentation/devicetree/bindings/iio/adc/rockchip-saradc.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-03-30 18:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 13:29 [PATCH v1 1/3] dt-bindings: iio: adc: convert rockchip saradc bindings to yaml Johan Jonker
2020-03-13 13:29 ` [PATCH v1 2/3] dt-bindings: iio: adc: rockchip-saradc: add description for rk3308 Johan Jonker
2020-03-30 18:10 ` Rob Herring
2020-04-04 14:02 ` Jonathan Cameron
2020-03-13 13:29 ` [PATCH v1 3/3] dt-bindings: iio: adc: rockchip-saradc: add description for px30 Johan Jonker
2020-03-30 18:11 ` Rob Herring
2020-04-04 14:02 ` Jonathan Cameron
2020-03-15 11:22 ` [PATCH v1 1/3] dt-bindings: iio: adc: convert rockchip saradc bindings to yaml Jonathan Cameron
2020-03-15 14:09 ` Heiko Stübner
2020-03-15 14:31 ` Jonathan Cameron
2020-03-15 14:11 ` Johan Jonker
2020-03-30 18:10 ` Rob Herring [this message]
2020-04-04 14:01 ` Jonathan Cameron
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=20200330181052.GA7527@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=pmeerw@pmeerw.net \
--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).