From: Shawn Guo <shawnguo@kernel.org>
To: Baoyou Xie <baoyou.xie@linaro.org>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Jun Nie <jun.nie@linaro.org>, Wolfram Sang <wsa@the-dreams.de>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm Mailing List <linux-arm-kernel@lists.infradead.org>,
linux-i2c@vger.kernel.org,
devicetree <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"xie.baoyou" <xie.baoyou@zte.com.cn>,
chen.chaokai@zte.com.cn, wang.qiang01@zte.com.cn
Subject: Re: [PATCH v4 3/3] i2c: zx2967: add i2c controller driver for ZTE's zx2967 family
Date: Tue, 7 Feb 2017 15:11:45 +0800 [thread overview]
Message-ID: <20170207071143.GF3407@dragon> (raw)
In-Reply-To: <CA+DQWkw70=cJUW4xbj91gMTpnfk4bOSgv9u9bv8427GjEVQoYA@mail.gmail.com>
On Mon, Feb 06, 2017 at 11:28:20AM +0800, Baoyou Xie wrote:
> + Shawn
>
> On 6 February 2017 at 11:26, Baoyou Xie <baoyou.xie@linaro.org> wrote:
>
> > This patch adds i2c controller driver for ZTE's zx2967 family.
> >
> > Signed-off-by: Baoyou Xie <baoyou.xie@linaro.org>
Reviewed-by: Shawn Guo <shawnguo@kernel.org>
next prev parent reply other threads:[~2017-02-07 7:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 3:26 [PATCH v4 1/3] dt: bindings: add documentation for zx2967 family i2c controller Baoyou Xie
2017-02-06 3:26 ` [PATCH v4 2/3] MAINTAINERS: add zx2967 i2c controller driver to ARM ZTE architecture Baoyou Xie
[not found] ` <1486351569-4814-1-git-send-email-baoyou.xie-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-02-06 3:26 ` [PATCH v4 3/3] i2c: zx2967: add i2c controller driver for ZTE's zx2967 family Baoyou Xie
[not found] ` <CA+DQWkw70=cJUW4xbj91gMTpnfk4bOSgv9u9bv8427GjEVQoYA@mail.gmail.com>
2017-02-07 7:11 ` Shawn Guo [this message]
2017-02-07 10:09 ` Jun Nie
2017-02-07 10:47 ` Andy Shevchenko
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=20170207071143.GF3407@dragon \
--to=shawnguo@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=baoyou.xie@linaro.org \
--cc=chen.chaokai@zte.com.cn \
--cc=devicetree@vger.kernel.org \
--cc=jun.nie@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=wang.qiang01@zte.com.cn \
--cc=wsa@the-dreams.de \
--cc=xie.baoyou@zte.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).