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
Subject: [PULL REQUEST] i2c for 4.10
Date: Sat, 28 Jan 2017 22:55:56 +0100 [thread overview]
Message-ID: <20170128215552.b2rufdbmi6bnuzxj@ninjato> (raw)
[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]
Linus,
here are two I2C driver bugfixes. The "VLLS mode support" patch should
have been entitled "reconfigure pinctrl after suspend" to make the
bugfix more clear. Sorry, I missed that, yet didn't want to rebase.
Please pull,
Wolfram
The following changes since commit 7a308bb3016f57e5be11a677d15b821536419d36:
Linux 4.10-rc5 (2017-01-22 12:54:15 -0800)
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 e13fe92bb58cf9b8f709ec18267ffc9e6ffeb016:
i2c: imx-lpi2c: add VLLS mode support (2017-01-26 00:24:23 +0100)
----------------------------------------------------------------
Gao Pan (1):
i2c: imx-lpi2c: add VLLS mode support
Mike Looijmans (1):
i2c: i2c-cadence: Initialize configuration before probing devices
with much appreciated quality assurance from
----------------------------------------------------------------
Vladimir Zapolskiy (1):
(Rev.) i2c: imx-lpi2c: add VLLS mode support
drivers/i2c/busses/i2c-cadence.c | 8 ++++----
drivers/i2c/busses/i2c-imx-lpi2c.c | 20 ++++++++++++++++++++
2 files changed, 24 insertions(+), 4 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2017-01-28 21:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-28 21:55 Wolfram Sang [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-17 11:19 [PULL REQUEST] i2c for 4.10 Wolfram Sang
2017-02-10 14:56 Wolfram Sang
2017-01-15 12:19 Wolfram Sang
2016-12-20 8:11 Wolfram Sang
2016-12-15 20:35 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=20170128215552.b2rufdbmi6bnuzxj@ninjato \
--to=wsa@the-dreams.de \
--cc=linux-i2c@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox