Linux IIO development
 help / color / mirror / Atom feed
From: Joe Simmons-Talbott <joetalbott@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org,
	"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
	"Tomasz Duszynski" <tomasz.duszynski@octakon.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>,
	"Siddartha Mohanadoss" <smohanad@codeaurora.org>
Subject: Re: [PATCH v2 0/4] 3rd set of IIO export namespaces.
Date: Mon, 20 Jun 2022 23:37:22 -0400	[thread overview]
Message-ID: <YrE88tt9469NSNno@spruce> (raw)
In-Reply-To: <20220618142054.4571f2f4@jic23-huawei>

On Sat, Jun 18, 2022 at 02:20:54PM +0100, Jonathan Cameron wrote:
> On Sat,  4 Jun 2022 16:53:02 +0100
> Jonathan Cameron <jic23@kernel.org> wrote:
> 
> > From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> > 
> > Changes since v1:
> > - Rebase (bit of fuzz in patches 1 and 4)
> 
> If anyone has time to take a quick look through this lot and sanity
> check I haven't done anything stupid it would be much appreciated.

FWIW, 1 through 4 look good to me.

Reviewed-By: Joe Simmons-Talbott <joetalbott@gmail.com>

Joe
> 
> Disadvantage of being the maintainer is there isn't anyone else you
> can moan about when no one reviews your patches. Of course I never
> moan about other maintainers and I'm sure no one ever moans
> about me :)
> 
> > 
> > I sent v1 out in Feb and only got review on one patch (which I've since
> > applied - thanks Nuno).
> > 
> > Looking for a quick sanity check of these 4 that remain from anyone who
> > has the time.  Whilst this is mechanical stuff, I've made enough dumb
> > mistakes in such patches over the years that I still like to get a second
> > set of eyes on them if at all possible! 
> > 
> > Cc: Tomasz Duszynski <tomasz.duszynski@octakon.com>
> > Cc: Nuno Sá <nuno.sa@analog.com>
> > Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> > Cc: Siddartha Mohanadoss <smohanad@codeaurora.org>
> > 
> > Jonathan Cameron (4):
> >   iio: imu: bmi160: Move exported symbols to IIO_BMI160 namespace
> >   iio: pressure: bmp280: Move symbol exports to IIO_BMP280 namespace
> >   iio: chemical: sps30: Move symbol exports into IIO_SPS30 namespace
> >   iio: adc: qcom-vadc: Move symbol exports to IIO_QCOM_VADC namespace
> > 
> >  drivers/iio/adc/qcom-pm8xxx-xoadc.c  |  1 +
> >  drivers/iio/adc/qcom-spmi-adc5.c     |  1 +
> >  drivers/iio/adc/qcom-spmi-vadc.c     |  1 +
> >  drivers/iio/adc/qcom-vadc-common.c   | 16 ++++++++--------
> >  drivers/iio/chemical/sps30.c         |  2 +-
> >  drivers/iio/chemical/sps30_i2c.c     |  1 +
> >  drivers/iio/chemical/sps30_serial.c  |  1 +
> >  drivers/iio/imu/bmi160/bmi160_core.c |  6 +++---
> >  drivers/iio/imu/bmi160/bmi160_i2c.c  |  1 +
> >  drivers/iio/imu/bmi160/bmi160_spi.c  |  1 +
> >  drivers/iio/pressure/bmp280-core.c   |  2 +-
> >  drivers/iio/pressure/bmp280-i2c.c    |  1 +
> >  drivers/iio/pressure/bmp280-regmap.c |  4 ++--
> >  drivers/iio/pressure/bmp280-spi.c    |  1 +
> >  14 files changed, 24 insertions(+), 15 deletions(-)
> > 
> 

  reply	other threads:[~2022-06-21  3:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-04 15:53 [PATCH v2 0/4] 3rd set of IIO export namespaces Jonathan Cameron
2022-06-04 15:53 ` [PATCH v2 1/4] iio: imu: bmi160: Move exported symbols to IIO_BMI160 namespace Jonathan Cameron
2022-06-04 15:53 ` [PATCH v2 2/4] iio: pressure: bmp280: Move symbol exports to IIO_BMP280 namespace Jonathan Cameron
2022-06-04 15:53 ` [PATCH v2 3/4] iio: chemical: sps30: Move symbol exports into IIO_SPS30 namespace Jonathan Cameron
2022-06-04 15:53 ` [PATCH v2 4/4] iio: adc: qcom-vadc: Move symbol exports to IIO_QCOM_VADC namespace Jonathan Cameron
2022-07-01 10:15   ` Jonathan Cameron
2022-06-18 13:20 ` [PATCH v2 0/4] 3rd set of IIO export namespaces Jonathan Cameron
2022-06-21  3:37   ` Joe Simmons-Talbott [this message]
2022-06-21 20:31     ` 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=YrE88tt9469NSNno@spruce \
    --to=joetalbott@gmail.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=smohanad@codeaurora.org \
    --cc=tomasz.duszynski@octakon.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