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 5.1
Date: Fri, 29 Mar 2019 16:16:50 +0100 [thread overview]
Message-ID: <20190329151647.GA4556@kunai> (raw)
[-- Attachment #1: Type: text/plain, Size: 2363 bytes --]
Linus,
I2C has for you:
A new ID for the i801 driver and some Documentation fixes to make it
easier for people to find the bindings (which is also a basis for
further improvements in that area).
Please pull.
Thanks,
Wolfram
The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
Linux 5.1-rc1 (2019-03-17 14:22:26 -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 080a910414659dfd18ffaf60a1e95b96c3f50eab:
i2c: wmt: make bindings file name match the driver (2019-03-27 14:20:20 +0100)
----------------------------------------------------------------
Jarkko Nikula (1):
i2c: i801: Add support for Intel Comet Lake
Wolfram Sang (5):
i2c: iop3xx: make bindings file name match the driver
i2c: mt65xx: make bindings file name match the driver
i2c: stu300: make bindings file name match the driver
i2c: sun6i-p2wi: make bindings file name match the driver
i2c: wmt: make bindings file name match the driver
with much appreciated quality assurance from
----------------------------------------------------------------
Jean Delvare (1):
(Rev.) i2c: i801: Add support for Intel Comet Lake
.../devicetree/bindings/i2c/{i2c-xscale.txt => i2c-iop3xx.txt} | 0
Documentation/devicetree/bindings/i2c/{i2c-mtk.txt => i2c-mt65xx.txt} | 0
.../devicetree/bindings/i2c/{i2c-st-ddci2c.txt => i2c-stu300.txt} | 0
.../bindings/i2c/{i2c-sunxi-p2wi.txt => i2c-sun6i-p2wi.txt} | 0
Documentation/devicetree/bindings/i2c/{i2c-vt8500.txt => i2c-wmt.txt} | 0
Documentation/i2c/busses/i2c-i801 | 1 +
drivers/i2c/busses/Kconfig | 1 +
drivers/i2c/busses/i2c-i801.c | 4 ++++
8 files changed, 6 insertions(+)
rename Documentation/devicetree/bindings/i2c/{i2c-xscale.txt => i2c-iop3xx.txt} (100%)
rename Documentation/devicetree/bindings/i2c/{i2c-mtk.txt => i2c-mt65xx.txt} (100%)
rename Documentation/devicetree/bindings/i2c/{i2c-st-ddci2c.txt => i2c-stu300.txt} (100%)
rename Documentation/devicetree/bindings/i2c/{i2c-sunxi-p2wi.txt => i2c-sun6i-p2wi.txt} (100%)
rename Documentation/devicetree/bindings/i2c/{i2c-vt8500.txt => i2c-wmt.txt} (100%)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2019-03-29 15:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 15:16 Wolfram Sang [this message]
2019-03-29 22:15 ` [PULL REQUEST] i2c for 5.1 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2019-05-03 16:21 Wolfram Sang
2019-05-03 19:05 ` pr-tracker-bot
2019-04-06 21:30 Wolfram Sang
2019-04-06 21:55 ` pr-tracker-bot
2019-03-15 11:00 Wolfram Sang
2019-03-15 21:45 ` pr-tracker-bot
2019-03-05 22:54 Wolfram Sang
2019-03-08 18:35 ` pr-tracker-bot
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=20190329151647.GA4556@kunai \
--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;
as well as URLs for NNTP newsgroup(s).