All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Linux IIO List <linux-iio@vger.kernel.org>
Subject: [PULL] IIO new drivers, features and cleanups for 3.16 - set 3
Date: Sun, 25 May 2014 12:28:06 +0100	[thread overview]
Message-ID: <5381D3C6.3040205@kernel.org> (raw)

The following changes since commit c4784756a53f7b17056f5d86fe0eb9740d235578:

   Merge branch 'imx-drm-fixes' of git://ftp.arm.linux.org.uk/~rmk/linux-arm into staging-next (2014-05-06 06:26:31 -0700)

are available in the git repository at:


   git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-for-3.16c

for you to fetch changes up to 34683a5c6e0ffaa61528ff71c283efe3063cc53f:

   fix format string missmatch in staging/iio/Documentation/iio_utils.h (2014-05-25 12:09:37 +0100)

----------------------------------------------------------------
Third round of new stuff for IIO in the 3.16 cycle.

This (rather late) set consists only of fixes to patches earlier in the
cycle or minor fixes for other problems (such as randconfig build issues
picked up by Arnd).  I've included the general minor fixes here as it is
very late in the current cycle and they can all wait for the merge window.

* Recent change to hid-sensors introduced a possible infinite loop due to a
   typo. In the same series, a report interval unit read was added but in the
   case where the hardware doesn't support it a value of 0 would lead to some
   nasty issues.  The patch sets it to the specified default of msecs.
* Anon inodes were used by IIO without being explicitly selected.  This has
   been true for a long time so it clearly only effects rather unusual
   configurations (rand configs)
* at91 requires the input subsytem but this wasn't explicity in the Kconfig.
* A couple of parts supported by the max1363 driver were using the wrong
   iio_chan_spec arrays and hence would missreport their bit depths.  This has
   been there a long time and was never right so isn't a regression.

----------------------------------------------------------------
Archana Patni (1):
       iio: hid-sensors: Set default unit of measure for report interval

Arnd Bergmann (2):
       iio: always select ANON_INODES
       iio:adc: at91 requires the input subsystem

Dan Carpenter (1):
       iio: hid-sensors: typo leads to potential forever loop

Jonathan Cameron (1):
       iio:adc:max1363 incorrect resolutions for max11604, max11605, max11610 and max11611.

Toralf Förster (1):
       fix format string missmatch in staging/iio/Documentation/iio_utils.h

  drivers/iio/Kconfig                                   |  1 +
  drivers/iio/adc/Kconfig                               |  1 +
  drivers/iio/adc/max1363.c                             | 16 ++++++++--------
  .../iio/common/hid-sensors/hid-sensor-attributes.c    | 19 ++++++++++++++++---
  drivers/staging/iio/Documentation/iio_utils.h         |  4 ++--
  5 files changed, 28 insertions(+), 13 deletions(-)

             reply	other threads:[~2014-05-25 11:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-25 11:28 Jonathan Cameron [this message]
2014-05-25 17:57 ` [PULL] IIO new drivers, features and cleanups for 3.16 - set 3 Greg Kroah-Hartman

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=5381D3C6.3040205@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.