From: Stephen Warren <swarren@wwwdotorg.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: khali@linux-fr.org, ben-linux@fluff.org, w.sang@pengutronix.de,
olof@lixom.net, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V1 2/2] i2c: tegra: notify transfer-complete after clearing status.
Date: Mon, 07 May 2012 10:19:52 -0600 [thread overview]
Message-ID: <4FA7F628.602@wwwdotorg.org> (raw)
In-Reply-To: <1336373179-12739-3-git-send-email-ldewangan@nvidia.com>
On 05/07/2012 12:46 AM, Laxman Dewangan wrote:
> The notification of the transfer complete by calling complete()
> should be done after clearing all interrupt status.
> This may avoid the race condition of misconfigure the i2c controller
> in multi-core environment.
>
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
Acked-by: Stephen Warren <swarren@wwwdotorg.org>
This patch appears to be independent from the first patch in the series,
so I assume can be checked in immediately.
next prev parent reply other threads:[~2012-05-07 16:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 6:46 [PATCH V1 1/2] i2c: tegra: make all resource allocation through devm_* Laxman Dewangan
2012-05-07 6:46 ` [PATCH V1 0/2] i2c: tegra: cleanup and bug fixes Laxman Dewangan
2012-05-07 6:46 ` [PATCH V1 2/2] i2c: tegra: notify transfer-complete after clearing status Laxman Dewangan
2012-05-07 16:19 ` Stephen Warren [this message]
2012-05-12 13:07 ` Wolfram Sang
2012-05-12 13:44 ` Laxman Dewangan
2012-05-12 14:11 ` Wolfram Sang
2012-05-07 16:18 ` [PATCH V1 1/2] i2c: tegra: make all resource allocation through devm_* Stephen Warren
2012-05-12 14:42 ` Wolfram Sang
-- strict thread matches above, loose matches on Subject: below --
2012-05-07 6:44 Laxman Dewangan
2012-05-07 6:44 ` [PATCH V1 2/2] i2c: tegra: notify transfer-complete after clearing status Laxman Dewangan
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=4FA7F628.602@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=ben-linux@fluff.org \
--cc=khali@linux-fr.org \
--cc=ldewangan@nvidia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=w.sang@pengutronix.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).