From: Christopher Covington <cov@codeaurora.org>
To: Pramod Gurav <pramod.gurav@smartplayin.com>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, Wolfram Sang <wsa@the-dreams.de>,
Grant Likely <grant.likely@linaro.org>,
Bjorn Andersson <bjorn.andersson@sonymobile.com>,
Andy Gross <agross@codeaurora.org>,
"Ivan T. Ivanov" <iivanov@mm-sol.com>
Subject: Re: [PATCH] i2c: qup: disable clks and return instead of just returning error
Date: Wed, 06 Aug 2014 08:19:31 -0400 [thread overview]
Message-ID: <53E21D53.30606@codeaurora.org> (raw)
In-Reply-To: <1407311602-15751-1-git-send-email-pramod.gurav@smartplayin.com>
Hi Pramod,
Not a big deal, but some typos caught my eye.
On 08/06/2014 03:53 AM, Pramod Gurav wrote:
> This fixes a error handling scenario where clocks were not being disabled
> when QUP_OUTPUT_BLOCK_SIZE returns a size greater thanat size of blk_sizes
s/thanat/than the/
> array. So this patch adds a statement to jump to err lable to release the
s/err lable/the error label/ or s/err lable/the fail label/
Regards,
Christopher
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.
next prev parent reply other threads:[~2014-08-06 12:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 7:53 [PATCH] i2c: qup: disable clks and return instead of just returning error Pramod Gurav
[not found] ` <1407311602-15751-1-git-send-email-pramod.gurav-edOiRQu9Xnj5XLMNweQjbQ@public.gmane.org>
2014-08-06 11:21 ` Ivan T. Ivanov
2014-08-06 12:19 ` Christopher Covington [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-08-06 12:33 Pramod Gurav
2014-08-09 19:32 ` Wolfram Sang
2014-08-06 7:48 Pramod Gurav
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=53E21D53.30606@codeaurora.org \
--to=cov@codeaurora.org \
--cc=agross@codeaurora.org \
--cc=bjorn.andersson@sonymobile.com \
--cc=grant.likely@linaro.org \
--cc=iivanov@mm-sol.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pramod.gurav@smartplayin.com \
--cc=wsa@the-dreams.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).