All of lore.kernel.org
 help / color / mirror / Atom feed
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 3.11 set 2
Date: Sun, 04 Aug 2013 17:37:58 +0100	[thread overview]
Message-ID: <51FE8366.8030207@kernel.org> (raw)

The following changes since commit 78077256bc08348d587e318957ceb41fe4d4afae:

  Merge tag 'iio-fixes-for-3.11a' of git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into staging-linus
(2013-07-16 22:41:38 -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.11b

for you to fetch changes up to b1451e546899bc8f450773b2af02e0cd000cf1fa:

  iio: ti_am335x_adc: Fix wrong samples received on 1st read (2013-07-21 18:27:35 +0100)

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

1) Fix a long term race in the IIO trigger handling.
   This only effects cases where a single trigger is in use
   by multiple devices.
2) ti_am335x fix an issue with incorrect data due to reading before
   the sequencer is finished.

----------------------------------------------------------------
Lars-Peter Clausen (1):
      iio:trigger: Fix use_count race condition

Patil, Rachna (1):
      iio: ti_am335x_adc: Fix wrong samples received on 1st read

 drivers/iio/adc/ti_am335x_adc.c      | 30 ++++++++++++++++++++++--------
 drivers/iio/industrialio-trigger.c   | 34 ++++++++++++++++++++++------------
 include/linux/iio/trigger.h          |  3 ++-
 include/linux/mfd/ti_am335x_tscadc.h | 16 ++++++++++++++++
 4 files changed, 62 insertions(+), 21 deletions(-)

             reply	other threads:[~2013-08-04 15:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-04 16:37 Jonathan Cameron [this message]
2013-08-05  6:08 ` [PULL] IIO fixes for 3.11 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=51FE8366.8030207@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.