public inbox for linux-kernel@vger.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>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Cc: devel@linuxdriverproject.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Staging fixes for 4.16-rc7
Date: Fri, 23 Mar 2018 14:32:26 +0100	[thread overview]
Message-ID: <20180323133226.GA27295@kroah.com> (raw)

The following changes since commit c698ca5278934c0ae32297a8725ced2e27585d7f:

  Linux 4.16-rc6 (2018-03-18 17:48:42 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/ tags/staging-4.16-rc7

for you to fetch changes up to 4c41aa24baa4ed338241d05494f2c595c885af8f:

  staging: ncpfs: memory corruption in ncp_read_kernel() (2018-03-19 16:31:39 +0100)

----------------------------------------------------------------
Staging/IIO fixes for 4.16-rc7

Here are a few small Staging and IIO fixes for various reported issues.

All of them are tiny, the majority being iio driver fixes for small
issues, and one staging driver fix for a memory corruption issue.

All have been in linux-next with no reported issues.

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

----------------------------------------------------------------
Dan Carpenter (2):
      iio: adc: meson-saradc: unlock on error in meson_sar_adc_lock()
      staging: ncpfs: memory corruption in ncp_read_kernel()

Fabrice Gasnier (5):
      iio: adc: stm32-dfsdm: fix compatible data use
      iio: adc: stm32-dfsdm: fix call to stop channel
      iio: adc: stm32-dfsdm: fix clock source selection
      iio: adc: stm32-dfsdm: fix multiple channel initialization
      dt-bindings: iio: adc: sd-modulator: fix io-channel-cells

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

Jonathan Cameron (1):
      Revert "iio: accel: st_accel: remove redundant pointer pdata"

Michael Nosthoff (1):
      iio: st_pressure: st_accel: pass correct platform data to init

Richard Lai (1):
      iio: chemical: ccs811: Corrected firmware boot/application mode transition

 .../bindings/iio/adc/sigma-delta-modulator.txt     |  4 +--
 drivers/iio/accel/st_accel_core.c                  |  7 +++-
 drivers/iio/adc/meson_saradc.c                     |  4 ++-
 drivers/iio/adc/stm32-dfsdm-adc.c                  | 39 ++++++++++++----------
 drivers/iio/adc/stm32-dfsdm-core.c                 | 12 +++++--
 drivers/iio/chemical/ccs811.c                      |  3 ++
 drivers/iio/pressure/st_pressure_core.c            |  2 +-
 drivers/staging/ncpfs/ncplib_kernel.c              |  4 +++
 8 files changed, 50 insertions(+), 25 deletions(-)
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

                 reply	other threads:[~2018-03-23 13:32 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=20180323133226.GA27295@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=devel@linuxdriverproject.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox