From: Rob Herring <robh@kernel.org>
To: Chris Ruehl <chris.ruehl@gtsys.com.hk>
Cc: "Hartmut Knaack" <knaack.h@gmx.de>,
linux-iio@vger.kernel.org, "Lars-Peter Clausen" <lars@metafoo.de>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Jonathan Cameron" <jic23@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
"Michael Hennerich" <michael.hennerich@analog.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Peter Meerwald-Stadler" <pmeerw@pmeerw.net>
Subject: Re: [PATCH] iio/dac: convert ltc2632.txt to lltc,ltc2632.yaml
Date: Mon, 24 Aug 2020 16:28:45 -0600 [thread overview]
Message-ID: <20200824222845.GA3434080@bogus> (raw)
In-Reply-To: <20200810033806.15503-1-chris.ruehl@gtsys.com.hk>
On Mon, 10 Aug 2020 11:37:52 +0800, Chris Ruehl wrote:
> Conversion of the ltc2632 to yaml format and name the file to
> 'lltc,ltc2632.yaml'.
>
> Signed-off-by: Chris Ruehl <chris.ruehl@gtsys.com.hk>
> ---
> v6:
> Remove tab and drop unused label
> Related patches already in linux-next.
> [PATCH v5 1/3] iio: documentation ltc2632_chip_info add num_channels
> linux-next commit: 6f1c9e0da9aae51177457731357ae8a2c8af27cd
> PATCH v5 2/3] iio: DAC extension for ltc2634-12/10/8
> linux-next commit: aefa5bc87c808dd08db2fc79ebdbf19ed4af7be2
>
> .../bindings/iio/dac/lltc,ltc2632.yaml | 77 +++++++++++++++++++
> .../devicetree/bindings/iio/dac/ltc2632.txt | 49 ------------
> 2 files changed, 77 insertions(+), 49 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/iio/dac/lltc,ltc2632.yaml
> delete mode 100644 Documentation/devicetree/bindings/iio/dac/ltc2632.txt
>
Reviewed-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2020-08-24 22:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 3:37 [PATCH] iio/dac: convert ltc2632.txt to lltc,ltc2632.yaml Chris Ruehl
2020-08-16 9:27 ` Jonathan Cameron
2020-08-18 0:19 ` Chris Ruehl
2020-08-24 22:28 ` Rob Herring
2020-08-24 22:28 ` Rob Herring [this message]
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=20200824222845.GA3434080@bogus \
--to=robh@kernel.org \
--cc=chris.ruehl@gtsys.com.hk \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=u.kleine-koenig@pengutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.