From: Jeff Garzik <jeff@garzik.org>
To: Trent Piepho <tpiepho@freescale.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] gianfar: Fix error in mdio reset timeout
Date: Wed, 24 Sep 2008 20:50:16 -0400 [thread overview]
Message-ID: <48DAE048.5020508@garzik.org> (raw)
In-Reply-To: <1222103036-27770-1-git-send-email-tpiepho@freescale.com>
Trent Piepho wrote:
> The loop with the timeout used "while (... && timeout--)", which means
> than when the timeout occurs, "timeout" will be -1 after the loop has
> exited. The code that checks if the looped exited because of a timeout
> used "if (timeout <= 0)". Seems ok, except timeout is unsigned, and
> (unsigned)-1 isn't less than zero!
>
> Using "--timeout" in the loop fixes this problem, as now "timeout" will be
> 0 when the loop times out.
>
> This also fixes a bug in the existing code, where it will erroneously think
> a timeout occurred if the condition the loop was waiting for is satisfied
> on the final iteration before a timeout.
>
> Signed-off-by: Trent Piepho <tpiepho@freescale.com>
> Acked-by: Andy Fleming <afleming@freescale.com>
> ---
> drivers/net/gianfar_mii.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/gianfar_mii.c b/drivers/net/gianfar_mii.c
> index ebcfb27..906aba2 100644
> --- a/drivers/net/gianfar_mii.c
> +++ b/drivers/net/gianfar_mii.c
> @@ -136,12 +136,12 @@ static int gfar_mdio_reset(struct mii_bus *bus)
>
> /* Wait until the bus is free */
> while ((gfar_read(®s->miimind) & MIIMIND_BUSY) &&
> - timeout--)
> + --timeout)
> cpu_relax();
>
> mutex_unlock(&bus->mdio_lock);
>
> - if(timeout <= 0) {
> + if(timeout == 0) {
> printk(KERN_ERR "%s: The MII Bus is stuck!\n",
applied
next prev parent reply other threads:[~2008-09-25 0:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 17:03 [PATCH] gianfar: Fix error in mdio reset timeout Trent Piepho
2008-09-25 0:50 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-06-10 23:36 Trent Piepho
2008-06-04 18:20 Trent Piepho
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=48DAE048.5020508@garzik.org \
--to=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=tpiepho@freescale.com \
/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).