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, 13 Jul 2018 22:34:23 +0200 [thread overview]
Message-ID: <20180713203419.ty2boi6zj6qvzyoh@katana> (raw)
[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]
Linus,
I2C has for you:
- one I2C core bugfix regarding bus recovery
- one driver bugfix for the tegra driver
- one typo correction
Please pull.
Thanks,
Wolfram
The following changes since commit 021c91791a5e7e85c567452f1be3e4c2c6cb6063:
Linux 4.18-rc3 (2018-07-01 16:04:53 -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 abe41184abac487264a4904bfcff2d5500dccce6:
i2c: recovery: if possible send STOP with recovery pulses (2018-07-12 23:38:18 +0200)
----------------------------------------------------------------
Jon Hunter (1):
i2c: tegra: Fix NACK error handling
Thadeu Lima de Souza Cascardo (1):
i2c: stu300: use non-archaic spelling of failes
Wolfram Sang (1):
i2c: recovery: if possible send STOP with recovery pulses
drivers/i2c/busses/i2c-stu300.c | 2 +-
drivers/i2c/busses/i2c-tegra.c | 17 ++++++++---------
drivers/i2c/i2c-core-base.c | 11 ++++++++++-
3 files changed, 19 insertions(+), 11 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2018-07-13 20:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 20:34 Wolfram Sang [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-08-10 10:58 [PULL REQUEST] i2c for 4.18 Wolfram Sang
2018-07-28 6:55 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=20180713203419.ty2boi6zj6qvzyoh@katana \
--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