From: Ralf Baechle <ralf@linux-mips.org>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-mips@linux-mips.org, linux-kernel@vger.kernel.org,
Richard Henderson <rth@twiddle.net>,
Geert Uytterhoeven <geert@linux-m68k.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: no-op delay loops
Date: Tue, 1 Dec 2015 02:25:46 +0100 [thread overview]
Message-ID: <20151201012546.GC23993@linux-mips.org> (raw)
In-Reply-To: <874mg3b2h5.fsf@rasmusvillemoes.dk>
On Mon, Nov 30, 2015 at 10:29:26PM +0100, Rasmus Villemoes wrote:
> OK, thanks. That's a very very long time ago.
>
> FWIW, the remaining instances that my trivial coccinelle script found
> are
After your initial report I also wrote a coccinelle which is looking
also for delay loops implemented in while loops. It found the following
two:
diff -u -p ./drivers/video/uvesafb.c /tmp/nothing/drivers/video/uvesafb.c
--- ./drivers/video/uvesafb.c
+++ /tmp/nothing/drivers/video/uvesafb.c
@@ -1142,7 +1142,6 @@ static int uvesafb_blank(int blank, stru
vga_wseq(NULL, 0x00, seq);
crtc17 |= vga_rcrt(NULL, 0x17) & ~0x80;
- while (loop--);
vga_wcrt(NULL, 0x17, crtc17);
vga_wseq(NULL, 0x00, 0x03);
} else
diff -u -p ./arch/mips/pmc-sierra/yosemite/atmel_read_eeprom.c /tmp/nothing/arch/mips/pmc-sierra/yosemite/atmel_read_eeprom.c
--- ./arch/mips/pmc-sierra/yosemite/atmel_read_eeprom.c
+++ /tmp/nothing/arch/mips/pmc-sierra/yosemite/atmel_read_eeprom.c
@@ -37,7 +37,6 @@
static void delay(int delay)
{
- while (delay--);
}
static void send_bit(unsigned char bit)
The 2nd file falls into my domain so I'm going to fix it. Not sure
how the uvesafb one should be treated.
Ralf
next prev parent reply other threads:[~2015-12-01 1:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 8:53 no-op delay loops Rasmus Villemoes
2015-11-27 9:04 ` yalin wang
2015-11-27 9:25 ` Andy Shevchenko
2015-11-27 11:17 ` Arnd Bergmann
2015-11-30 21:29 ` Rasmus Villemoes
2015-11-30 21:44 ` Arnd Bergmann
2015-12-01 1:25 ` Ralf Baechle [this message]
2015-12-01 15:31 ` Richard Henderson
2015-11-27 11:20 ` Ralf Baechle
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=20151201012546.GC23993@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux@rasmusvillemoes.dk \
--cc=rjw@rjwysocki.net \
--cc=rth@twiddle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.