All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, devel@linuxdriverproject.org
Subject: [GIT PULL] Staging/IIO driver fixes for 4.9-rc5
Date: Sun, 13 Nov 2016 11:16:17 +0100	[thread overview]
Message-ID: <20161113101617.GA7125@kroah.com> (raw)

The following changes since commit a909d3e636995ba7c349e2ca5dbb528154d4ac30:

  Linux 4.9-rc3 (2016-10-29 13:52:02 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/ tags/staging-4.9-rc5

for you to fetch changes up to d70674eeaa5efdefb99928691161578ae0a80316:

  iio: maxim_thermocouple: detect invalid storage size in read() (2016-11-13 10:08:32 +0100)

----------------------------------------------------------------
Staging/IIO fixes for 4.9-rc5

Here are a few small staging and iio driver fixes for reported issues.
The last one was cherry-picked from my -next branch to resolve a build
warning that Arnd fixed, in his quest to be able to turn
-Wmaybe-uninitialized back on again.  That patch, and all of the others,
have been in linux-next for a while with no reported issues.

Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

----------------------------------------------------------------
Arnd Bergmann (2):
      staging: iio: ad5933: avoid uninitialized variable in error case
      iio: maxim_thermocouple: detect invalid storage size in read()

Greg Kroah-Hartman (1):
      Merge tag 'iio-fixes-for-4.9b' of git://git.kernel.org/.../jic23/iio into staging-linus

Huacai Chen (1):
      staging: sm750fb: Fix bugs introduced by early commits

Ian Abbott (1):
      staging: comedi: ni_tio: fix buggy ni_tio_clock_period_ps() return value

Johan Hovold (1):
      staging: greybus: arche-platform: fix device reference leak

Lorenzo Bianconi (1):
      iio: st_sensors: fix scale configuration for h3lis331dl

Marc Dietrich (1):
      staging: nvec: remove managed resource from PS2 driver

Paul Fertser (2):
      drivers: staging: nvec: remove bogus reset command for PS/2 interface
      Revert "staging: nvec: ps2: change serio type to passthrough"

Song Hongyan (2):
      iio: orientation: hid-sensor-rotation: Add PM function (fix non working driver)
      iio: hid-sensors: Increase the precision of scale to fix wrong reading interpretation.

 drivers/iio/accel/st_accel_core.c                  | 12 +++--
 .../iio/common/hid-sensors/hid-sensor-attributes.c | 56 +++++++++++-----------
 drivers/iio/common/st_sensors/st_sensors_core.c    |  8 ++--
 drivers/iio/orientation/hid-sensor-rotation.c      |  1 +
 drivers/iio/temperature/maxim_thermocouple.c       |  2 +
 drivers/staging/comedi/drivers/ni_tio.c            |  3 +-
 drivers/staging/greybus/arche-platform.c           |  1 +
 drivers/staging/iio/impedance-analyzer/ad5933.c    | 17 ++++---
 drivers/staging/nvec/nvec_ps2.c                    |  8 +---
 drivers/staging/sm750fb/ddk750_reg.h               |  8 ++--
 10 files changed, 63 insertions(+), 53 deletions(-)

                 reply	other threads:[~2016-11-13 10:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20161113101617.GA7125@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=devel@linuxdriverproject.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.