From: Adrian Bunk <bunk@fs.tum.de>
To: Linus Torvalds <torvalds@transmeta.com>,
Rogier Wolff <R.E.Wolff@bitwizard.nl>,
Patrick van de Lageweg <patrick@bitwizard.nl>
Cc: linux-kernel@vger.kernel.org, <trivial@rustcorp.com.au>
Subject: [2.5 patch] don't #include tqueue.h in rio_linux.c
Date: Fri, 18 Oct 2002 18:50:10 +0200 (CEST) [thread overview]
Message-ID: <Pine.NEB.4.44.0210181846250.28761-100000@mimas.fachschaften.tu-muenchen.de> (raw)
Compilation of rio_linux.c fails in 2.5.43 with the following error:
<-- snip -->
...
gcc -Wp,-MD,drivers/char/rio/.rio_linux.o.d -D__KERNEL__ -Iinclude -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
-fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=k6
-Iarch/i386/mach-generic -nostdinc -iwithprefix include -DKBUILD_BASENAME=rio_linux -c -o
drivers/char/rio/rio_linux.o drivers/char/rio/rio_linux.c
drivers/char/rio/rio_linux.c:56: linux/tqueue.h: No such file or directory
make[3]: *** [drivers/char/rio/rio_linux.o] Error 1
<-- snip -->
With the following patch that removes the #include <linux/tqueue.h> it
compiles without errors or warnings:
--- linux-2.5.43-full/drivers/char/rio/rio_linux.c.old 2002-10-18 18:42:26.000000000 +0200
+++ linux-2.5.43-full/drivers/char/rio/rio_linux.c 2002-10-18 18:42:44.000000000 +0200
@@ -53,7 +53,6 @@
#include <linux/fcntl.h>
#include <linux/major.h>
#include <linux/delay.h>
-#include <linux/tqueue.h>
#include <linux/version.h>
#include <linux/pci.h>
#include <linux/slab.h>
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
reply other threads:[~2002-10-18 16:44 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.0210181846250.28761-100000@mimas.fachschaften.tu-muenchen.de \
--to=bunk@fs.tum.de \
--cc=R.E.Wolff@bitwizard.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick@bitwizard.nl \
--cc=torvalds@transmeta.com \
--cc=trivial@rustcorp.com.au \
/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).