From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Nicholas Mc Guire <hofrat@osadl.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: pxa3xx_nand: cleanup wait_for_completion handling
Date: Mon, 09 Feb 2015 10:00:29 -0300 [thread overview]
Message-ID: <54D8AF6D.3080001@free-electrons.com> (raw)
In-Reply-To: <1422809737-3991-1-git-send-email-hofrat@osadl.org>
On 02/01/2015 01:55 PM, Nicholas Mc Guire wrote:
> return type of wait_for_completion_timeout is unsigned long not int, this
> patch uses the return value of wait_for_completion_timeout in the condition
> directly rather than assigning it to an incorrect type variable.
>
> The timeout declaration cleanup is just for readability
>
> Signed-off-by: Nicholas Mc Guire <hofrat@osadl.org>
> ---
>
> The variable used for handling the return of wait_for_cmpletion_timeout
> was int but should be unsigned long, where it was not in use for anything
> else and the return value in case of completion (>0) is not used it was
> removed and wait_for_completion_timeout() used directly in the if condition.
>
> To make the timeout values a bit simpler to read and also handle all of
> the corner cases correctly the declarations are moved to msecs_to_jiffies().
>
Not sure why you decided to put this explanation outside of the commit log.
It looks useful so I'd move it up.
> This patch was only compile tested for pxa3xx_defconfig
> (implies CONFIG_MTD_NAND_PXA3xx=y)
>
The change looks good, but I would like someone to test it on real hardware.
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-02-09 13:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-01 16:55 [PATCH] mtd: pxa3xx_nand: cleanup wait_for_completion handling Nicholas Mc Guire
2015-02-09 13:00 ` Ezequiel Garcia [this message]
2015-02-09 15:01 ` Nicholas Mc Guire
2015-03-31 1:30 ` Brian Norris
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=54D8AF6D.3080001@free-electrons.com \
--to=ezequiel.garcia@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=hofrat@osadl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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