From: Jonathan Cameron <jic23@kernel.org>
To: Matt Ranostay <matt.ranostay@intel.com>
Cc: linux-iio@vger.kernel.org, daniel.baluta@intel.com,
adriana.reus@intel.com, Ge Gao <ggao@invensense.com>
Subject: Re: [PATCH 0/5] mpu6050: code clean and calibration support
Date: Wed, 24 Feb 2016 21:08:27 +0000 [thread overview]
Message-ID: <56CE1BCB.40807@kernel.org> (raw)
In-Reply-To: <1456177151-15881-1-git-send-email-matt.ranostay@intel.com>
On 22/02/16 21:39, Matt Ranostay wrote:
> The patchset series cleans up several documentation, return
> code issues, incorrect timing delays, and adds accl/gyro offset
> support.
>
> Matt Ranostay (5):
> iio: imu: mpu6050: use inv_mpu6050_sensor_show return code
> iio: imu: mpu6050: fix INV_MPU6050_REG_UP_TIME delay
> iio: imu: mpu6050: add missing docstring for int_pin_cfg
> iio: imu: mpu6050: add calibration offset support
> iio: imu: mpu6050: add mpu6500 register settings
>
> drivers/iio/imu/inv_mpu6050/inv_mpu_core.c | 88 +++++++++++++++++++++++++++---
> drivers/iio/imu/inv_mpu6050/inv_mpu_i2c.c | 6 +-
> drivers/iio/imu/inv_mpu6050/inv_mpu_iio.h | 20 ++++++-
> drivers/iio/imu/inv_mpu6050/inv_mpu_spi.c | 3 +-
> 4 files changed, 105 insertions(+), 12 deletions(-)
>
Whole series looks good to me (the typo fix can follow if you like :)
Ideally I'd like Ge to take a look as well (+ anyone else who fancies
doing so!) so will leave it on list for a few days more.
Jonathan
next prev parent reply other threads:[~2016-02-24 21:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 21:39 [PATCH 0/5] mpu6050: code clean and calibration support Matt Ranostay
2016-02-22 21:39 ` [PATCH 1/5] iio: imu: mpu6050: use inv_mpu6050_sensor_show return code Matt Ranostay
2016-02-22 21:49 ` Daniel Baluta
2016-02-22 21:50 ` Daniel Baluta
2016-02-25 19:50 ` Jonathan Cameron
2016-02-22 21:39 ` [PATCH 2/5] iio: imu: mpu6050: fix INV_MPU6050_REG_UP_TIME delay Matt Ranostay
2016-02-25 19:54 ` Jonathan Cameron
2016-02-22 21:39 ` [PATCH 3/5] iio: imu: mpu6050: add missing docstring for int_pin_cfg Matt Ranostay
2016-02-25 19:55 ` Jonathan Cameron
2016-02-22 21:39 ` [PATCH 4/5] iio: imu: mpu6050: add calibration offset support Matt Ranostay
2016-02-25 19:55 ` Jonathan Cameron
2016-02-22 21:39 ` [PATCH 5/5] iio: imu: mpu6050: add mpu6500 register settings Matt Ranostay
2016-02-25 19:56 ` Jonathan Cameron
2016-02-24 21:08 ` Jonathan Cameron [this message]
[not found] ` <DM3PR1201MB1072776083BB71F4F618555CAFA50@DM3PR1201MB1072.namprd12.prod.outlook.com>
2016-02-25 8:45 ` [PATCH 0/5] mpu6050: code clean and calibration support Daniel Baluta
2016-02-25 15:36 ` Ge Gao
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=56CE1BCB.40807@kernel.org \
--to=jic23@kernel.org \
--cc=adriana.reus@intel.com \
--cc=daniel.baluta@intel.com \
--cc=ggao@invensense.com \
--cc=linux-iio@vger.kernel.org \
--cc=matt.ranostay@intel.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;
as well as URLs for NNTP newsgroup(s).