From: David Brownell <david-b@pacbell.net>
To: Roel Kluin <roel.kluin@gmail.com>
Cc: spi-devel-general@lists.sourceforge.net,
lkml <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: pxa2xx_spi: spi_bfin5xx: limit reaches -1 rather than 0
Date: Sun, 8 Feb 2009 08:07:28 -0800 [thread overview]
Message-ID: <200902080807.29237.david-b@pacbell.net> (raw)
In-Reply-To: <498F0004.1030709@gmail.com>
On Sunday 08 February 2009, Roel Kluin wrote:
> vi drivers/spi/pxa2xx_spi.c +919
> vi drivers/spi/spi_bfin5xx.c +645
>
> if (flush(drv_data) == 0) {
> dev_err(&drv_data->pdev->dev, "pump_transfers: flush failed\n");
> message->status = -EIO;
> giveback(drv_data);
> return;
> }
>
> But with a postfix decrement limit reaches -1 rather than 0.
>
> Signed-off-by: Roel Kluin <roel.kluin@gmail.com>
Acked-by: David Brownell <dbrownell@users.sourceforge.net>
Although, note that if the *actual* count mattered here,
the correect patch would be to test "flush() < 0)" ...
except when using a "do {...} while (--limit)" idiom.
Try the thought experiment of starting with "limit = 1";
not all of these patches of your would go through the
loop even once. Fortunately in all these cases, the
limit is an arbitrary "don't loop forever" thing.
> ---
> drivers/spi/pxa2xx_spi.c | 2 +-
> drivers/spi/spi_bfin5xx.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/spi/pxa2xx_spi.c b/drivers/spi/pxa2xx_spi.c
> index d0fc4ca..3164741 100644
> --- a/drivers/spi/pxa2xx_spi.c
> +++ b/drivers/spi/pxa2xx_spi.c
> @@ -185,7 +185,7 @@ static int flush(struct driver_data *drv_data)
> while (read_SSSR(reg) & SSSR_RNE) {
> read_SSDR(reg);
> }
> - } while ((read_SSSR(reg) & SSSR_BSY) && limit--);
> + } while ((read_SSSR(reg) & SSSR_BSY) && --limit);
> write_SSSR(SSSR_ROR, reg);
>
> return limit;
> diff --git a/drivers/spi/spi_bfin5xx.c b/drivers/spi/spi_bfin5xx.c
> index 7fea3cf..ea94567 100644
> --- a/drivers/spi/spi_bfin5xx.c
> +++ b/drivers/spi/spi_bfin5xx.c
> @@ -162,7 +162,7 @@ static int flush(struct driver_data *drv_data)
> unsigned long limit = loops_per_jiffy << 1;
>
> /* wait for stop and clear stat */
> - while (!(read_STAT(drv_data) & BIT_STAT_SPIF) && limit--)
> + while (!(read_STAT(drv_data) & BIT_STAT_SPIF) && --limit)
> cpu_relax();
>
> write_STAT(drv_data, BIT_STAT_CLR);
>
>
next prev parent reply other threads:[~2009-02-08 16:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-08 15:53 pxa2xx_spi: spi_bfin5xx: limit reaches -1 rather than 0 Roel Kluin
2009-02-08 16:02 ` [PATCH v2] " Roel Kluin
2009-02-08 16:07 ` David Brownell [this message]
2009-02-08 16:59 ` roel kluin
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=200902080807.29237.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roel.kluin@gmail.com \
--cc=spi-devel-general@lists.sourceforge.net \
/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