All of lore.kernel.org
 help / color / mirror / Atom feed
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 for 3.10 - set 2
Date: Tue, 04 Jun 2013 19:30:58 +0100	[thread overview]
Message-ID: <51AE3262.6050906@kernel.org> (raw)

The following changes since commit e919b86c3b018c0e0c5e522354e743dcc0824ee1:

  staging: alarm-dev: information leak in alarm_ioctl() (2013-06-03 13:38:55 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-fixes-for-3.10b

for you to fetch changes up to 6c5d4c96f979611f0165dc825af9e1cea8dd35b9:

  iio:inkern: Fix typo/bug in convert raw to processed. (2013-06-04 18:46:45 +0100)

----------------------------------------------------------------
Second round of IIO fixes for the 3.10 cycle.

A couple of little bits and pieces, some delayed due to traveling.

1) A memory leak fix in the callback buffer.
2) Wrong exit path due to a return when it should have been a goto.
3) Bug in a mask value in ad4350
4) Reading the wrong value in raw to processed utility function.

----------------------------------------------------------------
Joe Perches (1):
      inkern: iio_device_put after incorrect return/goto

Jonathan Cameron (1):
      iio:callback buffer: free the scan_mask

Michael Hennerich (2):
      iio: frequency: ad4350: Fix bug / typo in mask
      iio:inkern: Fix typo/bug in convert raw to processed.

 drivers/iio/buffer_cb.c         | 5 ++++-
 drivers/iio/frequency/adf4350.c | 2 +-
 drivers/iio/inkern.c            | 4 ++--
 3 files changed, 7 insertions(+), 4 deletions(-)

             reply	other threads:[~2013-06-04 18:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-04 18:30 Jonathan Cameron [this message]
2013-06-04 19:31 ` [PULL] IIO fixes for 3.10 - 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=51AE3262.6050906@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.