All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Parthiban Nallathambi <pn@denx.de>
Cc: jic23@kernel.org, knaack.h@gmx.de, lars@metafoo.de,
	pmeerw@pmeerw.net, andy.shevchenko@gmail.com,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	mark.rutland@arm.com, devicetree@vger.kernel.org,
	matthias.bgg@gmail.com, wd@denx.de, sbabic@denx.de, hs@denx.de
Subject: Re: [PATCH v6 2/2] iio: light: Add device tree binding for vishay vcnl4035
Date: Tue, 7 Aug 2018 08:54:09 -0600	[thread overview]
Message-ID: <20180807145409.GA32028@rob-hp-laptop> (raw)
In-Reply-To: <20180807102704.1652656-2-pn@denx.de>

On Tue, Aug 07, 2018 at 12:27:04PM +0200, Parthiban Nallathambi wrote:
> Adding device tree binding for vcnl4035 and vendor
> prefix for Vishay Intertechnology
> 
> Signed-off-by: Parthiban Nallathambi <pn@denx.de>
> 
> Changelog in v3:
> - removed interrupt-parent property reference in documentation
> - renamed vcnl4035 to light-sensor
> 
> Changelog in v4:
> - commit message fix
> - same indexing/space in binding
> ---
>  .../devicetree/bindings/iio/light/vcnl4035.txt         | 18 ++++++++++++++++++
>  Documentation/devicetree/bindings/vendor-prefixes.txt  |  1 +
>  2 files changed, 19 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/iio/light/vcnl4035.txt

Reviewed-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2018-08-07 14:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-07 10:27 [PATCH v6 1/2] iio: light: Add support for vishay vcnl4035 Parthiban Nallathambi
2018-08-07 10:27 ` [PATCH v6 2/2] iio: light: Add device tree binding " Parthiban Nallathambi
2018-08-07 14:54   ` Rob Herring [this message]
2018-08-11 15:25 ` [PATCH v6 1/2] iio: light: Add support " kbuild test robot
2018-08-11 15:25   ` kbuild test robot
2018-08-19 17:35   ` Jonathan Cameron
2018-08-19 18:51 ` Jonathan Cameron
2018-08-19 21:50 ` Marcus Folkesson
2018-08-20  8:27   ` Parthiban Nallathambi

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=20180807145409.GA32028@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=andy.shevchenko@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hs@denx.de \
    --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=mark.rutland@arm.com \
    --cc=matthias.bgg@gmail.com \
    --cc=pmeerw@pmeerw.net \
    --cc=pn@denx.de \
    --cc=sbabic@denx.de \
    --cc=wd@denx.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.