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.6
Date: Wed, 27 Apr 2016 19:17:39 +0200 [thread overview]
Message-ID: <20160427171736.GA24920@katana> (raw)
[-- Attachment #1: Type: text/plain, Size: 1438 bytes --]
Linus,
I2C has one buildfix, one ABBA deadlock fix and three simple 'add ID'
patches for you. Please pull.
Thanks,
Wolfram
The following changes since commit bf16200689118d19de1b8d2a3c314fc21f5dc7bb:
Linux 4.6-rc3 (2016-04-10 17:58:30 -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 10ff4c5239a137abfc896ec73ef3d15a0f86a16a:
i2c: exynos5: Fix possible ABBA deadlock by keeping I2C clock prepared (2016-04-22 15:31:54 +0200)
----------------------------------------------------------------
Javier Martinez Canillas (1):
i2c: exynos5: Fix possible ABBA deadlock by keeping I2C clock prepared
Michael Ellerman (1):
i2c: cpm: Fix build break due to incompatible pointer types
Mika Westerberg (1):
i2c: ismt: Add Intel DNV PCI ID
Tanmay Jagdale (1):
i2c: xlp9xx: add support for Broadcom Vulcan
Yakir Yang (1):
i2c: rk3x: add support for rk3228
Documentation/devicetree/bindings/i2c/i2c-rk3x.txt | 4 ++--
drivers/i2c/busses/Kconfig | 4 ++--
drivers/i2c/busses/i2c-cpm.c | 4 ++--
drivers/i2c/busses/i2c-exynos5.c | 24 +++++++++++++++++-----
drivers/i2c/busses/i2c-ismt.c | 2 ++
drivers/i2c/busses/i2c-rk3x.c | 1 +
6 files changed, 28 insertions(+), 11 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2016-04-27 17:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 17:17 Wolfram Sang [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-04-10 7:31 [PULL REQUEST] i2c for 4.6 Wolfram Sang
2016-03-22 18: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=20160427171736.GA24920@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).