linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
	Peter Rosin <peda@axentia.se>,
	Bartosz Golaszewski <brgl@bgdev.pl>
Subject: [PULL REQUEST] i2c for v4.15
Date: Fri, 19 Jan 2018 15:29:37 +0100	[thread overview]
Message-ID: <20180119142933.jp2iwm36h4wbis3n@ninjato> (raw)

[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]

Linus,

here are two bugfixes for the I2C core: Lixing Wang fixed a refcounting
problem with DT nodes. Jeremy Compostella fixed a buffer overflow
possibility when using a 'don't use' ioctl interface directly.

Please pull.

Thanks,

   Wolfram


The following changes since commit a8750ddca918032d6349adbf9a4b6555e7db20da:

  Linux 4.15-rc8 (2018-01-14 15:32:30 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/for-current-fixed

for you to fetch changes up to 89c6efa61f5709327ecfa24bff18e57a4e80c7fa:

  i2c: core-smbus: prevent stack corruption on read I2C_BLOCK_DATA (2018-01-17 15:35:21 +0100)

----------------------------------------------------------------
Jeremy Compostella (1):
      i2c: core-smbus: prevent stack corruption on read I2C_BLOCK_DATA

Lixin Wang (1):
      i2c: core: decrease reference count of device node in i2c_unregister_device


with much appreciated quality assurance from
----------------------------------------------------------------
Wolfram Sang (1):
      (Test) i2c: core: decrease reference count of device node in i2c_unregister_device

 drivers/i2c/i2c-core-base.c  |  6 +++++-
 drivers/i2c/i2c-core-smbus.c | 13 +++++++------
 2 files changed, 12 insertions(+), 7 deletions(-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

                 reply	other threads:[~2018-01-19 14:29 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=20180119142933.jp2iwm36h4wbis3n@ninjato \
    --to=wsa@the-dreams.de \
    --cc=brgl@bgdev.pl \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peda@axentia.se \
    --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;
as well as URLs for NNTP newsgroup(s).