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.2
Date: Fri, 14 Jun 2019 18:45:53 +0200 [thread overview]
Message-ID: <20190614164549.GA6067@kunai> (raw)
[-- Attachment #1: Type: text/plain, Size: 995 bytes --]
Linus,
I2C has two simple but wanted driver fixes for you.
Please pull.
Thanks,
Wolfram
The following changes since commit d1fdb6d8f6a4109a4263176c84b899076a5f8008:
Linux 5.2-rc4 (2019-06-08 20:24:46 -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 a0cac264a86fbf4d6cb201fbbb73c1d335e3248a:
i2c: pca-platform: Fix GPIO lookup code (2019-06-12 12:54:06 +0200)
----------------------------------------------------------------
Linus Walleij (1):
i2c: pca-platform: Fix GPIO lookup code
Russell King (1):
i2c: acorn: fix i2c warning
with much appreciated quality assurance from
----------------------------------------------------------------
Chris Packham (1):
(Rev.) i2c: pca-platform: Fix GPIO lookup code
drivers/i2c/busses/i2c-acorn.c | 1 +
drivers/i2c/busses/i2c-pca-platform.c | 3 +--
2 files changed, 2 insertions(+), 2 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2019-06-14 16:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 16:45 Wolfram Sang [this message]
2019-06-15 1:55 ` [PULL REQUEST] i2c for 5.2 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2019-07-05 19:21 Wolfram Sang
2019-07-06 2:35 ` pr-tracker-bot
2019-06-08 8:54 Wolfram Sang
2019-06-08 20:10 ` pr-tracker-bot
2019-06-02 6:24 Wolfram Sang
2019-06-02 17:25 ` pr-tracker-bot
2019-05-18 11:01 Wolfram Sang
2019-05-19 19:15 ` pr-tracker-bot
2019-05-09 19:11 Wolfram Sang
2019-05-09 22:15 ` 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=20190614164549.GA6067@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).