From: Wolfram Sang <wsa@the-dreams.de>
To: Gao Pan <pandy.gao@nxp.com>
Cc: wsa-dev@sang-engineering.com, cmo@melexis.com, robh@kernel.org,
vz@mleia.com, linux-i2c@vger.kernel.org, frank.li@nxp.com,
fugang.duan@nxp.com
Subject: Re: [Patch V1] i2c: fsl-lpi2c: read lpi2c fifo size in probe()
Date: Sun, 11 Dec 2016 23:07:09 +0100 [thread overview]
Message-ID: <20161211220709.GI2552@katana> (raw)
In-Reply-To: <1480649896-5222-1-git-send-email-pandy.gao@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 316 bytes --]
On Fri, Dec 02, 2016 at 11:38:16AM +0800, Gao Pan wrote:
> The lpi2c fifo size is a read only parameter resides Parameter
> Register. It's better to read lpi2c tx/rx fifo size in probe()
> other than just define a macro for it.
>
> Signed-off-by: Gao Pan <pandy.gao@nxp.com>
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-12-11 22:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 3:38 [Patch V1] i2c: fsl-lpi2c: read lpi2c fifo size in probe() Gao Pan
2016-12-07 1:01 ` Vladimir Zapolskiy
2016-12-11 22:07 ` 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=20161211220709.GI2552@katana \
--to=wsa@the-dreams.de \
--cc=cmo@melexis.com \
--cc=frank.li@nxp.com \
--cc=fugang.duan@nxp.com \
--cc=linux-i2c@vger.kernel.org \
--cc=pandy.gao@nxp.com \
--cc=robh@kernel.org \
--cc=vz@mleia.com \
--cc=wsa-dev@sang-engineering.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