From: Adrian Bunk <bunk@fs.tum.de>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org, Jan Yenya Kasprzak <kas@fi.muni.cz>
Subject: [patch] fix 2.4.18-pre8 compile error in cosa.c
Date: Tue, 5 Feb 2002 15:56:32 +0100 (CET) [thread overview]
Message-ID: <Pine.NEB.4.44.0202051546330.24218-100000@mimas.fachschaften.tu-muenchen.de> (raw)
Hi Marcelo,
the patch below fixes the following compile error in 2.4.18-pre8:
<-- snip -->
gcc -D__KERNEL__ -I/home/bunk/linux/kernel-2.4/linux/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
-fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
-march=k6 -DKBUILD_BASENAME=cosa -c -o cosa.o cosa.c
cosa.c:109: parse error
<-- snip -->
Line 109 is
#if LINUX_VERSION_CODE < KERNEL_VERSION(2,3,1)
I was first thinking about including linux/version.h to fix it but since
in another place where there's in the cosa.c in kernel 2.2.20 a check for
2.2 kernels the code for the older kernels was already removed in the
cosa.c in kernel 2.4.18-pre8 I assume that it's no longer intended to use
this version of the file in 2.2 kernels.
--- drivers/net/wan/cosa.c.old Tue Feb 5 15:37:20 2002
+++ drivers/net/wan/cosa.c Tue Feb 5 15:47:37 2002
@@ -105,13 +105,6 @@
#include <net/syncppp.h>
#include "cosa.h"
-/* Linux version stuff */
-#if LINUX_VERSION_CODE < KERNEL_VERSION(2,3,1)
-typedef struct wait_queue *wait_queue_head_t;
-#define DECLARE_WAITQUEUE(wait, current) \
- struct wait_queue wait = { current, NULL }
-#endif
-
/* Maximum length of the identification string. */
#define COSA_MAX_ID_STRING 128
cu
Adrian
next reply other threads:[~2002-02-05 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 14:56 Adrian Bunk [this message]
2002-02-05 15:00 ` [patch] fix 2.4.18-pre8 compile error in cosa.c Jan Kasprzak
2002-02-05 18:12 ` Marcelo Tosatti
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.0202051546330.24218-100000@mimas.fachschaften.tu-muenchen.de \
--to=bunk@fs.tum.de \
--cc=kas@fi.muni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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).