From: Wolfram Sang <wsa@the-dreams.de>
To: Peter Rosin <peda@axentia.se>
Cc: linux-kernel@vger.kernel.org,
Vadim Pasternak <vadimp@mellanox.com>,
Michael Shych <michaelsh@mellanox.com>,
Guenter Roeck <linux@roeck-us.net>,
Akinobu Mita <akinobu.mita@gmail.com>,
Jean Delvare <jdelvare@suse.com>,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH 0/5] i2c: smbus: add unlocked __i2c_smbus_xfer variant
Date: Tue, 3 Jul 2018 23:01:00 +0200 [thread overview]
Message-ID: <20180703210100.jpxz4xwwwgvjqycv@ninjato> (raw)
In-Reply-To: <20180620085157.30121-1-peda@axentia.se>
[-- Attachment #1: Type: text/plain, Size: 802 bytes --]
On Wed, Jun 20, 2018 at 10:51:52AM +0200, Peter Rosin wrote:
> Hi!
>
> There are a couple of users that could benefit from an unlocked variant
> of i2c_smbus_xfer. In response to [1] I dusted off an old series that I
> have had in a branch for a while that adds such a beast. It also converts
> over some users in the i2c-mux department.
>
> There are a couple of remaining candidates in i2c/busses/i2c-amd756-s4882.c
> and i2c/busses/i2c-nforce2-s4985.c, but frankly, those are just too nasty.
> Why do they unregister the root adapter and then continue to use it? I
> dare not touch that code...
>
> Anyway, this series looks like a nice cleanup to me, and the recent sccb
> patch from Akinobu Mita could also benefit, as indicated by Wolfram [1].
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-07-03 21:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 8:51 [PATCH 0/5] i2c: smbus: add unlocked __i2c_smbus_xfer variant Peter Rosin
2018-06-20 8:51 ` [PATCH 1/5] " Peter Rosin
2018-06-26 2:37 ` Wolfram Sang
2018-06-26 11:54 ` Peter Rosin
2018-06-26 13:46 ` Wolfram Sang
2018-06-27 4:18 ` Peter Rosin
2018-06-27 7:08 ` Wolfram Sang
2018-07-01 12:13 ` Wolfram Sang
2018-07-01 16:40 ` Peter Rosin
2018-06-20 8:51 ` [PATCH 2/5] i2c: mux: mlxcpld: make use of __i2c_smbus_xfer Peter Rosin
2018-06-20 9:11 ` Michael Shych
2018-06-20 8:51 ` [PATCH 3/5] i2c: mux: pca9541: " Peter Rosin
2018-06-20 8:51 ` [PATCH 4/5] i2c: mux: pca954x: " Peter Rosin
2018-06-20 8:51 ` [PATCH 5/5] i2c: mux: " Peter Rosin
2018-07-03 21:01 ` Wolfram Sang [this message]
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=20180703210100.jpxz4xwwwgvjqycv@ninjato \
--to=wsa@the-dreams.de \
--cc=akinobu.mita@gmail.com \
--cc=jdelvare@suse.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=michaelsh@mellanox.com \
--cc=peda@axentia.se \
--cc=vadimp@mellanox.com \
/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).