From: John Williams <john.williams@petalogix.com>
To: microblaze-uclinux@itee.uq.edu.au
Cc: monstr@monstr.eu, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [microblaze-uclinux] [PATCH] microblaze: iowrite upon timeout
Date: Tue, 21 Apr 2009 11:18:59 +1000 [thread overview]
Message-ID: <1d3f23370904201818v1efb272dv55441d436311a19@mail.gmail.com> (raw)
In-Reply-To: <49E799CD.1010902@gmail.com>
On Fri, Apr 17, 2009 at 6:49 AM, Roel Kluin <roel.kluin@gmail.com> wrote:
> retries reaches -1, so the iowrite occurrs upon timeout.
>
> Signed-off-by: Roel Kluin <roel.kluin@gmail.com>
Acked-by: John Williams <john.williams@petalogix.com>
(also applied to PetaLogix SVN)
Thanks,
John
> ---
> diff --git a/arch/microblaze/kernel/early_printk.c b/arch/microblaze/kernel/early_printk.c
> index 62cc789..4b0f0fd 100644
> --- a/arch/microblaze/kernel/early_printk.c
> +++ b/arch/microblaze/kernel/early_printk.c
> @@ -36,7 +36,7 @@ static void early_printk_putc(char c)
>
> unsigned retries = 10000;
> /* read status bit - 0x8 offset */
> - while (retries-- && (in_be32(base_addr + 8) & (1 << 3)))
> + while (--retries && (in_be32(base_addr + 8) & (1 << 3)))
> ;
>
> /* Only attempt the iowrite if we didn't timeout */
> ___________________________
> microblaze-uclinux mailing list
> microblaze-uclinux@itee.uq.edu.au
> Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
> Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
>
>
--
John Williams, PhD, B.Eng, B.IT
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663 f: +61-7-30090663
prev parent reply other threads:[~2009-04-21 1:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 20:49 Roel Kluin
2009-04-21 1:18 ` John Williams [this message]
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=1d3f23370904201818v1efb272dv55441d436311a19@mail.gmail.com \
--to=john.williams@petalogix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=monstr@monstr.eu \
/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
all inboxes | Powered by JetHome®