From: Jonathan Cameron <jic23@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: [PULL] Second set of IIO fixes for the 4.5 cycle - dependent on merge window patches.
Date: Mon, 1 Feb 2016 20:21:52 +0000 [thread overview]
Message-ID: <56AFBE60.7030509@kernel.org> (raw)
The following changes since commit 02c34ccc1d2d528d2de2897881b97933363432b5:
Merge tag 'iio-for-4.5c' of git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into staging-next (2015-12-26 17:05:25 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-fixes-for-4.5b
for you to fetch changes up to 17a2f46c3d8877fe2a0b6ff391d1df30e67892a6:
iio: dht11: Use boottime (2016-02-01 20:16:13 +0000)
----------------------------------------------------------------
Second set of IIO fixes for the 4.5 cycle. These ones are mostly
dependent on patches from the recent merge cycle.
* adc, imu and iio staging drivers
- !HAS_IOMEM dependency fixes
* dht11
- use boottime clock for time measurement to avoid incorrect measurements
due to clock updates.
* lidar
- correct a return value for short i2c transfers.
----------------------------------------------------------------
Abhilash Jindal (1):
iio: dht11: Use boottime
Matt Ranostay (1):
iio: proximity: lidar: correct return value
Richard Weinberger (3):
iio: adc: Fix dependencies for !HAS_IOMEM archs
staging: iio: Fix dependencies for !HAS_IOMEM archs
iio: imu: Fix dependencies for !HAS_IOMEM archs
drivers/iio/adc/Kconfig | 3 +++
drivers/iio/humidity/dht11.c | 8 ++++----
drivers/iio/imu/inv_mpu6050/Kconfig | 2 +-
drivers/iio/proximity/pulsedlight-lidar-lite-v2.c | 2 +-
drivers/staging/iio/adc/Kconfig | 1 +
5 files changed, 10 insertions(+), 6 deletions(-)
next reply other threads:[~2016-02-01 20:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 20:21 Jonathan Cameron [this message]
2016-02-01 21:09 ` [PULL] Second set of IIO fixes for the 4.5 cycle - dependent on merge window patches Greg KH
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=56AFBE60.7030509@kernel.org \
--to=jic23@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-iio@vger.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).