From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: clock-mx28: Fix end of loop condition
Date: Mon, 16 Jan 2012 22:19:25 +0100 [thread overview]
Message-ID: <201201162219.25838.marek.vasut@gmail.com> (raw)
In-Reply-To: <20120116210700.GA5823@pengutronix.de>
> On Mon, Jan 16, 2012 at 06:55:04PM -0200, Fabio Estevam wrote:
> > On Mon, Jan 16, 2012 at 6:52 PM, Marek Vasut <marek.vasut@gmail.com> wrote:
> > > I see ... ignore my previous comment ;-)
> >
> > Sorry for the noise of my previous patch. I think this issue can be
> > solved by just increasing the timeout value.
> >
> > I will make more tests to confirm and post a new patch.
>
> Please make it proper and use some real timeout value (measured in us)
> instead of this random loop counter.
Good point
next prev parent reply other threads:[~2012-01-16 21:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 19:01 [PATCH] ARM: clock-mx28: Fix end of loop condition Fabio Estevam
2012-01-16 20:32 ` Fabio Estevam
2012-01-16 20:52 ` Marek Vasut
2012-01-16 20:55 ` Fabio Estevam
2012-01-16 21:07 ` Wolfram Sang
2012-01-16 21:19 ` Marek Vasut [this message]
2012-01-17 15:24 ` Fabio Estevam
2012-01-17 17:17 ` Fabio Estevam
2012-01-16 20:52 ` Marek Vasut
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=201201162219.25838.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).