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, 15 Mar 2019 12:00:14 +0100 [thread overview]
Message-ID: <20190315110010.GA2084@kunai> (raw)
[-- Attachment #1: Type: text/plain, Size: 2362 bytes --]
Linus,
I2C has a set of driver bugfixes and an improvement for a core helper which
would be nice to have in your tree before rc1.
Please pull.
Thanks,
Wolfram
The following changes since commit ea295481b6e313b4ea3ca2720ffcafd6005b5643:
Merge tag 'xarray-5.1-rc1' of git://git.infradead.org/users/willy/linux-dax (2019-03-11 20:06:18 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/for-current-fixed
for you to fetch changes up to cd86d1403bb4c80e443d736b2a692cbf68a9f471:
i2c: i2c-designware-platdrv: Always use a dynamic adapter number (2019-03-13 18:07:10 +0100)
----------------------------------------------------------------
Hans de Goede (2):
i2c: i2c-designware-platdrv: Cleanup setting of the adapter number
i2c: i2c-designware-platdrv: Always use a dynamic adapter number
Hiromitsu Yamasaki (1):
i2c: rcar: fix concurrency issue related to ICDMAER
Hsin-Yi Wang (1):
i2c: mediatek: modify threshold passed to i2c_get_dma_safe_msg_buf()
Louis Taylor (1):
i2c: sis630: correct format strings
Nicolas Le Bayon (1):
i2c: i2c-stm32f7: Fix SDADEL minimum formula
Wolfram Sang (2):
i2c: rcar: explain the lockless design
i2c: add extra check to safe DMA buffer helper
with much appreciated quality assurance from
----------------------------------------------------------------
Andy Shevchenko (1):
(Rev.) i2c: i2c-designware-platdrv: Cleanup setting of the adapter number
Hsin-Yi Wang (1):
(Rev.) i2c: add extra check to safe DMA buffer helper
Jean Delvare (1):
(Rev.) i2c: sis630: correct format strings
Nick Desaulniers (1):
(Rev.) i2c: sis630: correct format strings
Pierre-Yves MORDRET (1):
(Rev.) i2c: i2c-stm32f7: Fix SDADEL minimum formula
Simon Horman (2):
(Rev.) i2c: rcar: explain the lockless design
(Rev.) i2c: rcar: fix concurrency issue related to ICDMAER
drivers/i2c/busses/i2c-designware-platdrv.c | 7 +++----
drivers/i2c/busses/i2c-mt65xx.c | 8 ++++----
drivers/i2c/busses/i2c-rcar.c | 15 ++++++++++++---
drivers/i2c/busses/i2c-sis630.c | 4 ++--
drivers/i2c/busses/i2c-stm32f7.c | 2 +-
drivers/i2c/i2c-core-base.c | 9 +++++++--
6 files changed, 29 insertions(+), 16 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2019-03-15 11:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 11:00 Wolfram Sang [this message]
2019-03-15 21:45 ` [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-29 15:16 Wolfram Sang
2019-03-29 22:15 ` 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=20190315110010.GA2084@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).