From: Vladimir Zapolskiy <vz@mleia.com>
To: Peter Rosin <peda@axentia.se>, linux-kernel@vger.kernel.org
Cc: Guenter Roeck <linux@roeck-us.net>,
Wolfram Sang <wsa@the-dreams.de>,
Ken Chen <chen.kenyy@inventec.com>,
joel@jms.id.au, linux-i2c@vger.kernel.org
Subject: Re: [PATCH 3/3] i2c: mux: pca9541: prepare for PCA9641 support
Date: Wed, 21 Mar 2018 09:05:09 +0200 [thread overview]
Message-ID: <7c14645a-3166-c793-550f-0db8cdfd8873@mleia.com> (raw)
In-Reply-To: <20180320093200.19179-4-peda@axentia.se>
On 03/20/2018 11:32 AM, Peter Rosin wrote:
> Make the arbitrate and release_bus implementation chip specific.
>
> Signed-off-by: Peter Rosin <peda@axentia.se>
Reviewed-by: Vladimir Zapolskiy <vz@mleia.com>
The change is really good and correct, it is just too extended IMHO.
--
With best wishes,
Vladimir
next prev parent reply other threads:[~2018-03-21 7:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 6:19 [PATCH linux dev-4.16 v2] i2c: muxes: pca9641: new driver Ken Chen
2018-03-20 6:34 ` Joel Stanley
2018-03-20 9:31 ` Peter Rosin
2018-03-20 9:31 ` [PATCH 1/3] i2c: mux: pca9541: use the BIT macro Peter Rosin
2018-03-20 13:18 ` Guenter Roeck
2018-03-20 23:25 ` Vladimir Zapolskiy
2018-03-20 9:31 ` [PATCH 2/3] i2c: mux: pca9541: namespace cleanup Peter Rosin
2018-03-20 13:20 ` Guenter Roeck
2018-03-20 21:48 ` Peter Rosin
2018-03-20 21:57 ` Guenter Roeck
2018-03-20 23:24 ` Vladimir Zapolskiy
2018-03-21 5:53 ` Peter Rosin
2018-03-21 6:54 ` Vladimir Zapolskiy
2018-03-21 7:35 ` Peter Rosin
2018-03-20 9:32 ` [PATCH 3/3] i2c: mux: pca9541: prepare for PCA9641 support Peter Rosin
2018-03-20 13:22 ` Guenter Roeck
2018-03-20 23:17 ` Vladimir Zapolskiy
2018-03-21 1:19 ` Guenter Roeck
2018-03-21 7:01 ` Vladimir Zapolskiy
2018-03-21 8:09 ` Peter Rosin
2018-03-21 7:05 ` Vladimir Zapolskiy [this message]
2018-04-11 9:37 ` [PATCH linux dev-4.16 v2] i2c: muxes: pca9641: new driver Peter Rosin
2018-04-13 6:59 ` ChenKenYY 陳永營 TAO
2018-04-13 7:27 ` Peter Rosin
2018-04-16 7:37 ` ChenKenYY 陳永營 TAO
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=7c14645a-3166-c793-550f-0db8cdfd8873@mleia.com \
--to=vz@mleia.com \
--cc=chen.kenyy@inventec.com \
--cc=joel@jms.id.au \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=peda@axentia.se \
--cc=wsa@the-dreams.de \
/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).