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 4.19
Date: Fri, 31 Aug 2018 14:41:23 +0200 [thread overview]
Message-ID: <20180831124120.suchscewwcrta476@ninjato> (raw)
[-- Attachment #1: Type: text/plain, Size: 2275 bytes --]
Linus,
I2C has for you:
* regression fixes for i801 and designware
* better API and leak fix for releasing DMA safe buffers
* better greppable strings for the bitbang algorithm
Thanks,
Wolfram
The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
Linux 4.19-rc1 (2018-08-26 14:11:59 -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 cebc07d84ad71bc58d6f59b770e4347da48a5a2b:
i2c: sh_mobile: fix leak when using DMA bounce buffer (2018-08-30 23:13:59 +0200)
----------------------------------------------------------------
Hans de Goede (1):
i2c: designware: Re-init controllers with pm_disabled set on resume
Jan Kundrát (1):
i2c: algos: bit: make the error messages grepable
Mika Westerberg (1):
i2c: i801: Allow ACPI AML access I/O ports not reserved for SMBus
Wolfram Sang (3):
i2c: refactor function to release a DMA safe buffer
i2c: sh_mobile: define start_ch() void as it only returns 0 anyhow
i2c: sh_mobile: fix leak when using DMA bounce buffer
with much appreciated quality assurance from
----------------------------------------------------------------
Andy Shevchenko (1):
(Rev.) i2c: designware: Re-init controllers with pm_disabled set on resume
Jean Delvare (1):
(Rev.) i2c: i801: Allow ACPI AML access I/O ports not reserved for SMBus
Niklas Söderlund (3):
(Rev.) i2c: sh_mobile: fix leak when using DMA bounce buffer
(Rev.) i2c: sh_mobile: define start_ch() void as it only returns 0 anyhow
(Rev.) i2c: refactor function to release a DMA safe buffer
Documentation/i2c/DMA-considerations | 10 ++++--
drivers/i2c/algos/i2c-algo-bit.c | 55 ++++++++++++++++-------------
drivers/i2c/busses/i2c-designware-master.c | 1 -
drivers/i2c/busses/i2c-designware-platdrv.c | 7 +++-
drivers/i2c/busses/i2c-i801.c | 9 ++++-
drivers/i2c/busses/i2c-sh_mobile.c | 15 ++++----
drivers/i2c/i2c-core-base.c | 11 +++---
include/linux/i2c.h | 2 +-
8 files changed, 66 insertions(+), 44 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2018-08-31 12:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 12:41 Wolfram Sang [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-10-21 10:40 [PULL REQUEST] i2c for 4.19 Wolfram Sang
2018-10-21 19:49 ` Greg KH
2018-10-13 16:21 Wolfram Sang
2018-10-14 6:55 ` Greg KH
2018-10-06 20:37 Wolfram Sang
2018-10-07 5:21 ` Greg KH
2018-09-07 19:55 Wolfram Sang
2018-08-24 15:37 Wolfram Sang
2018-08-27 13:58 ` Jean Delvare
2018-08-21 14:04 Wolfram Sang
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=20180831124120.suchscewwcrta476@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).