From: Adrian Bunk <bunk@fs.tum.de>
To: claus@momo.math.rwth-aachen.de
Cc: linux-kernel@vger.kernel.org
Subject: [patch] remove a workaround for gcc-2.4.5
Date: Wed, 23 Jan 2002 22:08:05 +0100 (CET) [thread overview]
Message-ID: <Pine.NEB.4.44.0201232200370.14017-100000@mimas.fachschaften.tu-muenchen.de> (raw)
Hi Claus-Justus,
the patch below removes a workaround for gcc-2.4.5. Since a long time
passed since this compiler was supported the last time this could be IMHO
removed from the 2.2/2.4/2.5 kernels.
cu
Adrian
--- drivers/char/ftape/lowlevel/fdc-io.c.old Wed Jan 23 21:59:13 2002
+++ drivers/char/ftape/lowlevel/fdc-io.c Wed Jan 23 22:00:39 2002
@@ -928,18 +928,6 @@
set_dma_mode(fdc.dma, mode);
set_dma_addr(fdc.dma, virt_to_bus((void*)addr));
set_dma_count(fdc.dma, count);
-#ifdef GCC_2_4_5_BUG
- /* This seemingly stupid construction confuses the gcc-2.4.5
- * code generator enough to create correct code.
- */
- if (1) {
- int i;
-
- for (i = 0; i < 1; ++i) {
- ftape_udelay(1);
- }
- }
-#endif
enable_dma(fdc.dma);
}
reply other threads:[~2002-01-23 21:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.NEB.4.44.0201232200370.14017-100000@mimas.fachschaften.tu-muenchen.de \
--to=bunk@fs.tum.de \
--cc=claus@momo.math.rwth-aachen.de \
--cc=linux-kernel@vger.kernel.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).