From: Rob Herring <robh+dt@kernel.org>
To: Brian Masney <masneyb@onstation.org>
Cc: Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald <pmeerw@pmeerw.net>,
Mark Rutland <mark.rutland@arm.com>,
Anson Huang <anson.huang@nxp.com>,
"open list:IIO SUBSYSTEM AND DRIVERS" <linux-iio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
devicetree@vger.kernel.org,
Laxman Dewangan <ldewangan@nvidia.com>,
Rhyland Klein <rklein@nvidia.com>
Subject: Re: [PATCH] dt-bindings: iio: isl29018: convert bindings to YAML format
Date: Mon, 29 Apr 2019 07:44:14 -0500 [thread overview]
Message-ID: <CAL_Jsq+Wzc8W11E0XYg5bKfGoYNxFu0U0-Rdk5PqXZf40W21ZA@mail.gmail.com> (raw)
In-Reply-To: <20190427182359.27254-1-masneyb@onstation.org>
On Sat, Apr 27, 2019 at 1:25 PM Brian Masney <masneyb@onstation.org> wrote:
>
> Convert the isl29018 device tree bindings to the new YAML format.
>
> Signed-off-by: Brian Masney <masneyb@onstation.org>
> ---
> I'm willing to be listed as the maintainer since this is one of the
> drivers that I moved out out of staging unless one of the original
> authors wants to be listed instead.
>
> I added the BSD-2-Clause to the new binding document. I wrote the
> original document and the only commit since then was from Rob in
> commit 791d3ef2e111 ("dt-bindings: remove 'interrupt-parent' from
> bindings")
>
> .../bindings/iio/light/isl29018.txt | 27 ---------
> .../bindings/iio/light/isl29018.yaml | 56 +++++++++++++++++++
> 2 files changed, 56 insertions(+), 27 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/iio/light/isl29018.txt
> create mode 100644 Documentation/devicetree/bindings/iio/light/isl29018.yaml
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-04-29 12:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-27 18:23 Brian Masney
2019-04-29 12:44 ` Rob Herring [this message]
2019-05-05 11:42 ` 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=CAL_Jsq+Wzc8W11E0XYg5bKfGoYNxFu0U0-Rdk5PqXZf40W21ZA@mail.gmail.com \
--to=robh+dt@kernel.org \
--cc=anson.huang@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=ldewangan@nvidia.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=masneyb@onstation.org \
--cc=pmeerw@pmeerw.net \
--cc=rklein@nvidia.com \
/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
all inboxes | Powered by JetHome®