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] IIO fixes v3.5-rc4
Date: Sat, 30 Jun 2012 13:24:24 +0100 [thread overview]
Message-ID: <4FEEEFF8.8050305@kernel.org> (raw)
Hi Greg,
Please consider pulling the following fixes.
I've based these on your staging-linus branch which happens
right now to be v3.5-rc4.
None are exactly critical if you want to hold them for the next
merge window.
Obviously any suggestions / requests on how to do these pull
requests welcomed!
The following changes since commit 6b16351acbd415e66ba16bf7d473ece1574cf0bc:
Linux 3.5-rc4 (2012-06-24 12:53:04 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git fixes-togreg
for you to fetch changes up to 06d5199d4c53615338d0453b62458cd82fb88f33:
staging:iio: Add some missing peak elements to the info_mask
(2012-06-30 10:12:36 +0100)
----------------------------------------------------------------
Jonathan Cameron (2):
staging:iio:accel:adis16204 fix bug in channel modifier handling
staging:iio: Add some missing peak elements to the info_mask
Lars-Peter Clausen (1):
staging:iio:ad7793: Fix scan index for the "shorted" channel
Peter Meerwald (3):
iio staging: fix potential resource leak in generic_buffer
iio staging: fix potential memory/resource leaks in
find_type_by_name()
iio staging: fix resource leak in _write_sysfs_int()
drivers/staging/iio/Documentation/iio_utils.h | 24 +++++++++++++++++++-----
drivers/staging/iio/accel/adis16204_core.c | 2 +-
drivers/staging/iio/accel/adis16240_core.c | 9 ++++++---
drivers/staging/iio/adc/ad7793.c | 4 ++--
4 files changed, 28 insertions(+), 11 deletions(-)
next reply other threads:[~2012-06-30 12:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-30 12:24 Jonathan Cameron [this message]
2012-07-06 23:03 ` [PULL] IIO fixes v3.5-rc4 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=4FEEEFF8.8050305@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 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.