From: Jonathan Cameron <jic23@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Ivan Mikhaylov <i.mikhaylov@yadro.com>,
linux-kernel@vger.kernel.org, Hartmut Knaack <knaack.h@gmx.de>,
linux-iio@vger.kernel.org,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
devicetree@vger.kernel.org, Lars-Peter Clausen <lars@metafoo.de>,
Mark Rutland <mark.rutland@arm.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v14 1/2] dt-bindings: proximity: provide vcnl3020 device tree binding document
Date: Thu, 21 May 2020 19:11:14 +0100 [thread overview]
Message-ID: <20200521191114.6b454ab9@archlinux> (raw)
In-Reply-To: <20200518204144.GA11276@bogus>
On Mon, 18 May 2020 14:41:44 -0600
Rob Herring <robh@kernel.org> wrote:
> On Sun, 10 May 2020 21:45:36 +0300, Ivan Mikhaylov wrote:
> > Mostly standard i2c driver with some additional led-current option
> > for vcnl3020.
> >
> > Signed-off-by: Ivan Mikhaylov <i.mikhaylov@yadro.com>
> > ---
> > .../iio/proximity/vishay,vcnl3020.yaml | 62 +++++++++++++++++++
> > 1 file changed, 62 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/iio/proximity/vishay,vcnl3020.yaml
> >
>
> Reviewed-by: Rob Herring <robh@kernel.org>
Applied to the togreg branch of iio.git and pushed out as testing for
the autobuilders to play with it.
Thanks,
Jonathan
next prev parent reply other threads:[~2020-05-21 18:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-10 18:45 [PATCH v14 0/2] iio: proximity: driver for vcnl3020 Ivan Mikhaylov
2020-05-10 18:45 ` [PATCH v14 1/2] dt-bindings: proximity: provide vcnl3020 device tree binding document Ivan Mikhaylov
2020-05-18 20:41 ` Rob Herring
2020-05-21 18:11 ` Jonathan Cameron [this message]
2020-05-10 18:45 ` [PATCH v14 2/2] iio: proximity: Add driver support for vcnl3020 proximity sensor Ivan Mikhaylov
2020-05-21 18:14 ` Jonathan Cameron
2020-05-16 16:41 ` [PATCH v14 0/2] iio: proximity: driver for vcnl3020 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=20200521191114.6b454ab9@archlinux \
--to=jic23@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=i.mikhaylov@yadro.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=robh@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).