From: Andy Gross <andy.gross@linaro.org>
To: Sricharan R <sricharan@codeaurora.org>
Cc: iivanov@mm-sol.com, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org, galak@codeaurora.org,
linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
agross@codeaurora.org, dmaengine@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [V5, 1/6] i2c: qup: Change qup_wait_writeready function to use for all timeouts
Date: Mon, 4 Jan 2016 21:19:44 -0600 [thread overview]
Message-ID: <20160105031944.GA4139@hector.attlocal.net> (raw)
In-Reply-To: <1447760727-4897-2-git-send-email-sricharan@codeaurora.org>
On Tue, Nov 17, 2015 at 05:15:22PM +0530, Sricharan R wrote:
> qup_wait_writeready waits only on a output fifo empty event.
> Change the same function to accept the event and data length
> to wait as parameters. This way the same function can be used for
> timeouts in other places as well.
>
> Signed-off-by: Sricharan R <sricharan@codeaurora.org>
Looks good to me.
Reviewed-by: Andy Gross <andy.gross@linaro.org>
next prev parent reply other threads:[~2016-01-05 3:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 11:45 [PATCH V5 0/6] i2c: qup: Add support for v2 tags and bam dma Sricharan R
2015-11-17 11:45 ` [PATCH V5 1/6] i2c: qup: Change qup_wait_writeready function to use for all timeouts Sricharan R
2016-01-05 3:19 ` Andy Gross [this message]
2015-11-17 11:45 ` [PATCH V5 2/6] i2c: qup: Add V2 tags support Sricharan R
2015-11-17 11:45 ` [PATCH V5 3/6] i2c: qup: Transfer each i2c_msg in i2c_msgs without a stop bit Sricharan R
2016-01-09 4:36 ` [V5, " Andy Gross
2015-11-17 11:45 ` [PATCH V5 4/6] i2c: qup: Add bam dma capabilities Sricharan R
2016-01-09 4:38 ` [V5,4/6] " Andy Gross
2015-11-17 11:45 ` [PATCH V5 5/6] dts: msm8974: Add blsp2_bam dma node Sricharan R
2016-01-09 4:39 ` [V5,5/6] " Andy Gross
2015-11-17 11:45 ` [PATCH V5 6/6] dts: msm8974: Add dma channels for blsp2_i2c1 node Sricharan R
2016-01-09 4:40 ` [V5,6/6] " Andy Gross
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=20160105031944.GA4139@hector.attlocal.net \
--to=andy.gross@linaro.org \
--cc=agross@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=iivanov@mm-sol.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sricharan@codeaurora.org \
/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