From: Wolfram Sang <wsa@kernel.org>
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 v5.13
Date: Fri, 25 Jun 2021 17:32:43 +0200 [thread overview]
Message-ID: <YNX3G9fQKWX+45gJ@shikoro> (raw)
[-- Attachment #1: Type: text/plain, Size: 1751 bytes --]
Linus,
I2C has three more driver bugfixes and a annotation fix for the core.
Please pull.
Thanks,
Wolfram
The following changes since commit 009c9aa5be652675a06d5211e1640e02bbb1c33d:
Linux 5.13-rc6 (2021-06-13 14:43:10 -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 4ca070ef0dd885616ef294d269a9bf8e3b258e1a:
i2c: robotfuzz-osif: fix control-request directions (2021-06-24 22:08:00 +0200)
----------------------------------------------------------------
Andreas Hecht (1):
i2c: dev: Add __user annotation
Dan Carpenter (1):
i2c: cp2615: check for allocation failure in cp2615_i2c_recv()
Heiner Kallweit (1):
i2c: i801: Ensure that SMBHSTSTS_INUSE_STS is cleared when leaving i801_access
Johan Hovold (1):
i2c: robotfuzz-osif: fix control-request directions
with much appreciated quality assurance from
----------------------------------------------------------------
Bence Csókás (1):
(Rev.) i2c: cp2615: check for allocation failure in cp2615_i2c_recv()
Hector Martin (1):
(Rev.) i2c: i801: Ensure that SMBHSTSTS_INUSE_STS is cleared when leaving i801_access
Jean Delvare (2):
(Rev.) i2c: i801: Ensure that SMBHSTSTS_INUSE_STS is cleared when leaving i801_access
(Test) i2c: i801: Ensure that SMBHSTSTS_INUSE_STS is cleared when leaving i801_access
drivers/i2c/busses/i2c-cp2615.c | 14 ++++++++++----
drivers/i2c/busses/i2c-i801.c | 3 +++
drivers/i2c/busses/i2c-robotfuzz-osif.c | 4 ++--
drivers/i2c/i2c-dev.c | 2 +-
4 files changed, 16 insertions(+), 7 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2021-06-25 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-25 15:32 Wolfram Sang [this message]
2021-06-25 17:49 ` [PULL REQUEST] i2c for v5.13 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=YNX3G9fQKWX+45gJ@shikoro \
--to=wsa@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.