public inbox for linux-i2c@vger.kernel.org
 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 4.18
Date: Fri, 10 Aug 2018 12:58:43 +0200	[thread overview]
Message-ID: <20180810105840.bajsbm3dx3myusji@ninjato> (raw)

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

Linus,

here is a driver bugfix for I2C. The bug was found by systematically
stress testing the driver, so I am confident to merge it that late in
the cycle although it is probably unusually large.

Please pull.

Thanks,

   Wolfram


The following changes since commit 1ffaddd029c867d134a1dde39f540dcc8c52e274:

  Linux 4.18-rc8 (2018-08-05 12:37:41 -0700)

are available in the git repository at:

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

for you to fetch changes up to 5eb173f5c8f3a3cdc47b3952c368f10a28c81ab8:

  i2c: xlp9xx: Fix case where SSIF read transaction completes early (2018-08-09 17:41:13 +0200)

----------------------------------------------------------------
George Cherian (1):
      i2c: xlp9xx: Fix case where SSIF read transaction completes early

 drivers/i2c/busses/i2c-xlp9xx.c | 41 ++++++++++++++++++++++++++++-------------
 1 file changed, 28 insertions(+), 13 deletions(-)

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

             reply	other threads:[~2018-08-10 10:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-10 10:58 Wolfram Sang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-07-28  6:55 [PULL REQUEST] i2c for 4.18 Wolfram Sang
2018-07-13 20:34 Wolfram Sang
2018-06-29 15:13 Wolfram Sang
2018-06-13  9:21 Wolfram Sang

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=20180810105840.bajsbm3dx3myusji@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