All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Song Qiang <songqiang1304521@gmail.com>,
	knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
	mark.rutland@arm.com, andriy.shevchenko@linux.intel.com,
	matt.ranostay@konsulko.com, tglx@linutronix.de, ak@it-klinger.de,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, himanshujha199640@gmail.com,
	Song Qiang <songqiang.1304521@gmail.com>
Subject: Re: [PATCH v5] iio: proximity: Add driver support for ST's VL53L0X ToF ranging sensor.
Date: Sat, 22 Sep 2018 16:24:37 +0100	[thread overview]
Message-ID: <20180922162437.224e574c@archlinux> (raw)
In-Reply-To: <20180917061933.GA15262@bogus>

...
> > 
> >  .../bindings/iio/proximity/vl53l0x.txt        |  12 ++
> >  MAINTAINERS                                   |   7 +  
> 
> Otherwise,
> 
> Reviewed-by: Rob Herring <robh@kernel.org>
Hi Song,

Please make sure to pick up the various Acks, Reviewed-bys etc for later versions.

I've added this to the version I applied.

Thanks,

Jonathan
> 
> >  drivers/iio/proximity/Kconfig                 |  11 ++
> >  drivers/iio/proximity/Makefile                |   2 +
> >  drivers/iio/proximity/vl53l0x-i2c.c           | 180 ++++++++++++++++++
> >  5 files changed, 212 insertions(+)
> >  create mode 100644 Documentation/devicetree/bindings/iio/proximity/vl53l0x.txt
> >  create mode 100644 drivers/iio/proximity/vl53l0x-i2c.c  

      parent reply	other threads:[~2018-09-22 21:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-15  9:57 [PATCH v5] iio: proximity: Add driver support for ST's VL53L0X ToF ranging sensor Song Qiang
2018-09-16 11:01 ` Jonathan Cameron
2018-09-16 13:36   ` Song Qiang
2018-09-17  8:25     ` Jonathan Cameron
2018-09-17  8:25       ` Jonathan Cameron
2018-09-17 13:33       ` Song Qiang
2018-09-17  6:19 ` Rob Herring
2018-09-17  7:38   ` Song Qiang
2018-09-22 15:24   ` Jonathan Cameron [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=20180922162437.224e574c@archlinux \
    --to=jic23@kernel.org \
    --cc=ak@it-klinger.de \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=himanshujha199640@gmail.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=matt.ranostay@konsulko.com \
    --cc=pmeerw@pmeerw.net \
    --cc=robh@kernel.org \
    --cc=songqiang.1304521@gmail.com \
    --cc=songqiang1304521@gmail.com \
    --cc=tglx@linutronix.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.