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.0
Date: Sun, 17 Feb 2019 11:15:17 +0100 [thread overview]
Message-ID: <20190217101513.mmbztn2nopa4phif@ninjato> (raw)
[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]
Linus,
I2C has two more driver bugfixes for you.
Please pull.
Thanks,
Wolfram
The following changes since commit d13937116f1e82bf508a6325111b322c30c85eb9:
Linux 5.0-rc6 (2019-02-10 14:42:20 -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 f275a4659484716259cc46268d9043424e51cf0f:
i2c: bcm2835: Clear current buffer pointers and counts after a transfer (2019-02-15 09:45:05 +0100)
----------------------------------------------------------------
Paul Kocialkowski (1):
i2c: bcm2835: Clear current buffer pointers and counts after a transfer
Shubhrajyoti Datta (1):
i2c: cadence: Fix the hold bit setting
with much appreciated quality assurance from
----------------------------------------------------------------
Kyle Roeschley (1):
(Test) i2c: cadence: Fix the hold bit setting
drivers/i2c/busses/i2c-bcm2835.c | 12 ++++++++++++
drivers/i2c/busses/i2c-cadence.c | 9 +++++++--
2 files changed, 19 insertions(+), 2 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2019-02-17 10:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-17 10:15 Wolfram Sang [this message]
2019-02-17 16:50 ` [PULL REQUEST] i2c for 5.0 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2019-01-11 18:56 Wolfram Sang
2019-01-11 20:40 ` 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=20190217101513.mmbztn2nopa4phif@ninjato \
--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).