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.8
Date: Sat, 24 Sep 2016 01:36:31 +0200 [thread overview]
Message-ID: <20160923233627.GA6259@katana> (raw)
[-- Attachment #1: Type: text/plain, Size: 1149 bytes --]
Linus,
I2C has 3 driver bugfixes for you, fixing uninitialized memory pointers
(eg20t), pm/clock imbalance (qup), and a wrongly set cached variable
(pc954x). Please pull.
Thanks,
Wolfram
The following changes since commit 3be7988674ab33565700a37b210f502563d932e6:
Linux 4.8-rc7 (2016-09-18 17:27: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 331dcf421c34d227784d07943eb01e4023a42b0a:
i2c: qup: skip qup_i2c_suspend if the device is already runtime suspended (2016-09-22 20:11:14 +0200)
----------------------------------------------------------------
Peter Rosin (1):
i2c: mux: pca954x: retry updating the mux selection on failure
Sudeep Holla (1):
i2c: qup: skip qup_i2c_suspend if the device is already runtime suspended
Yadi.hu (1):
i2c-eg20t: fix race between i2c init and interrupt enable
drivers/i2c/busses/i2c-eg20t.c | 18 +++++++++++-------
drivers/i2c/busses/i2c-qup.c | 3 ++-
drivers/i2c/muxes/i2c-mux-pca954x.c | 2 +-
3 files changed, 14 insertions(+), 9 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2016-09-23 23:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 23:36 Wolfram Sang [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-09-10 14:07 [PULL REQUEST] i2c for 4.8 Wolfram Sang
2016-08-19 18:28 Wolfram Sang
2016-07-27 21:05 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=20160923233627.GA6259@katana \
--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;
as well as URLs for NNTP newsgroup(s).