From: Jonathan Cameron <jic23@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: [PULL] IIO fixes for v3.6-rc1 set 2
Date: Mon, 03 Sep 2012 21:03:21 +0100 [thread overview]
Message-ID: <50450D09.5060206@kernel.org> (raw)
The following changes since commit 95d1c8c7e26e303ccab5b65fe0ce04f70f42ea8a:
iio: lm3533-als: Fix build warnings (2012-08-16 20:24:38 +0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/v3.6-rc1-iio-fixes-2
for you to fetch changes up to f755bbbf1f9f180aa61eb730d638b62e225bfc10:
drivers/iio/adc/at91_adc.c: adjust inconsistent IS_ERR and PTR_ERR (2012-08-27 21:15:25 +0100)
----------------------------------------------------------------
IIO fixes for v3.6-rc1 set 2
A few simple fixes.
1)Fix up some possible divide by zero issues in various drivers.
2)Prevent a memory leak in an error path in lis3l02dq
3)Make sure the PTR_ERR call in at91_adc matches the
check for IS_ERR just above it rather than using a different
pointer.
Merges fine against v3.6rc4
----------------------------------------------------------------
Dan Carpenter (1):
staging:iio: prevent divide by zero bugs
Julia Lawall (1):
drivers/iio/adc/at91_adc.c: adjust inconsistent IS_ERR and PTR_ERR
Peter Meerwald (1):
staging iio: fix potential memory leak in lis3l02dq_ring.c
drivers/iio/adc/at91_adc.c | 2 +-
drivers/staging/iio/accel/lis3l02dq_ring.c | 4 +++-
drivers/staging/iio/adc/ad7192.c | 2 ++
drivers/staging/iio/gyro/adis16260_core.c | 2 ++
drivers/staging/iio/imu/adis16400_core.c | 2 ++
drivers/staging/iio/meter/ade7753.c | 2 ++
drivers/staging/iio/meter/ade7754.c | 2 ++
drivers/staging/iio/meter/ade7759.c | 2 ++
8 files changed, 16 insertions(+), 2 deletions(-)
next reply other threads:[~2012-09-03 20:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 20:03 Jonathan Cameron [this message]
2012-09-04 19:10 ` [PULL] IIO fixes for v3.6-rc1 set 2 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=50450D09.5060206@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