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.16
Date: Fri, 3 Dec 2021 17:45:26 +0100 [thread overview]
Message-ID: <YapJpi/BNwQ3VOR/@kunai> (raw)
[-- Attachment #1: Type: text/plain, Size: 1699 bytes --]
Linus,
I2C has another set of driver bugfixes, mostly for the stm32f7 driver.
Please pull.
Thanks,
Wolfram
The following changes since commit d58071a8a76d779eedab38033ae4c821c30295a5:
Linux 5.16-rc3 (2021-11-28 14:09:19 -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 02fe0fbd8a21e183687925c3a266ae27dda9840f:
i2c: rk3x: Handle a spurious start completion interrupt flag (2021-11-30 22:38:15 +0100)
----------------------------------------------------------------
Aaro Koskinen (1):
i2c: cbus-gpio: set atomic transfer callback
Alain Volmat (4):
i2c: stm32f7: flush TX FIFO upon transfer errors
i2c: stm32f7: recover the bus on access timeout
i2c: stm32f7: stop dma transfer in case of NACK
i2c: stm32f7: use proper DMAENGINE API for termination
Ondrej Jirman (1):
i2c: rk3x: Handle a spurious start completion interrupt flag
with much appreciated quality assurance from
----------------------------------------------------------------
John Keeping (1):
(Rev.) i2c: rk3x: Handle a spurious start completion interrupt flag
Pierre-Yves MORDRET (4):
(Rev.) i2c: stm32f7: use proper DMAENGINE API for termination
(Rev.) i2c: stm32f7: stop dma transfer in case of NACK
(Rev.) i2c: stm32f7: recover the bus on access timeout
(Rev.) i2c: stm32f7: flush TX FIFO upon transfer errors
drivers/i2c/busses/i2c-cbus-gpio.c | 5 +++--
drivers/i2c/busses/i2c-rk3x.c | 4 ++--
drivers/i2c/busses/i2c-stm32f7.c | 45 ++++++++++++++++++++++++++++++++------
3 files changed, 43 insertions(+), 11 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2021-12-03 16:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 16:45 Wolfram Sang [this message]
2021-12-03 18:53 ` [PULL REQUEST] i2c for v5.16 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2022-01-08 18:10 Wolfram Sang
2022-01-08 20:19 ` pr-tracker-bot
2022-01-01 22:05 Wolfram Sang
2022-01-02 18:38 ` pr-tracker-bot
2021-12-11 8:50 Wolfram Sang
2021-12-11 17:28 ` pr-tracker-bot
2021-11-26 10:38 Wolfram Sang
2021-11-26 18:35 ` pr-tracker-bot
2021-11-08 8:28 Wolfram Sang
2021-11-08 20:27 ` pr-tracker-bot
2021-11-06 21:33 Wolfram Sang
2021-11-07 19:14 ` 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=YapJpi/BNwQ3VOR/@kunai \
--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.