From: Shawn Guo <shawnguo@kernel.org>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Shawn Guo <shawn.guo@linaro.org>,
Baoyou Xie <xie.baoyou@sanechips.com.cn>,
linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Xin Zhou <zhou.xin8@sanechips.com.cn>
Subject: Re: [PATCH 0/2] Add I2C driver for ZTE ZX2967 family SoCs
Date: Sat, 10 Jun 2017 22:32:08 +0800 [thread overview]
Message-ID: <20170610143207.GA9839@dragon> (raw)
In-Reply-To: <1495947576-11037-1-git-send-email-shawnguo@kernel.org>
Hi Wolfram,
On Sun, May 28, 2017 at 12:59:34PM +0800, Shawn Guo wrote:
> From: Shawn Guo <shawn.guo@linaro.org>
>
> Hi Wolfram,
>
> The ZX2967 I2C driver submission had gone through quite a number of
> review iterations [1], and seems close to be accepted. But for some
> reason, the ball got dropped from there. I'm here to pick it up and
> hopefully move it forward.
>
> This is basically a resend of the latest posting from Baoyou with
> Wolfram's comments on v7 fully addressed.
>
> Changes since v7:
> - Rebase and test on v4.12-rc2.
> - Drop the dev_err() and hardware reset on timeout, which is not really
> necessary.
> - Return -ETIMEDOUT instead of -EIO on timeout.
> - Unify zx2967_i2c_xfer_write_bytes() and zx2967_i2c_xfer_read_bytes()
> into one function zx2967_i2c_xfer_bytes(), and zx2967_i2c_xfer_write()
> and zx2967_i2c_xfer_read() into zx2967_i2c_xfer_msg().
Any comments on the series? We hope it can get into v4.13 merge window.
Shawn
prev parent reply other threads:[~2017-06-10 14:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-28 4:59 [PATCH 0/2] Add I2C driver for ZTE ZX2967 family SoCs Shawn Guo
2017-05-28 4:59 ` [PATCH 1/2] dt: bindings: add documentation for zx2967 family i2c controller Shawn Guo
2017-05-28 4:59 ` [PATCH 2/2] i2c: zx2967: add i2c controller driver for ZTE's zx2967 family Shawn Guo
2017-06-19 19:31 ` Wolfram Sang
2017-06-20 2:58 ` Shawn Guo
2017-06-20 7:41 ` Wolfram Sang
2017-06-21 16:06 ` Shawn Guo
2017-06-22 7:48 ` Shawn Guo
2017-06-22 8:07 ` Wolfram Sang
2017-06-22 12:25 ` Shawn Guo
2017-06-22 13:22 ` Wolfram Sang
2017-06-10 14:32 ` Shawn Guo [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=20170610143207.GA9839@dragon \
--to=shawnguo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=shawn.guo@linaro.org \
--cc=wsa@the-dreams.de \
--cc=xie.baoyou@sanechips.com.cn \
--cc=zhou.xin8@sanechips.com.cn \
/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).