From: Adrian Bunk <bunk@fs.tum.de>
To: Marcelo Tosatti <marcelo@conectiva.com.br>, jt@hpl.hp.com
Cc: linux-kernel@vger.kernel.org, trivial@rustcorp.com.au
Subject: [2.4 patch] fix wavelan_cs compile warning
Date: Sat, 24 May 2003 10:46:06 +0200 [thread overview]
Message-ID: <20030524084605.GD1824@fs.tum.de> (raw)
I saw the following compile warning in 2.4.21-rc3:
<-- snip -->
...
make[3]: Entering directory `/home/bunk/linux/kernel-2.4/linux-2.4.21-rc3-modular/drivers/net/pcmcia'
...
gcc -D__KERNEL__
-I/home/bunk/linux/kernel-2.4/linux-2.4.21-rc3-modular/include
-Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing
-fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -DMODULE -DMODVERSIONS
-include /home/bunk/linux/kernel-2.4/linux-2.4.21-rc3-modular/include/linux/modversions.h
-nostdinc -iwithprefix include -DKBUILD_BASENAME=wavelan_cs -c -o
wavelan_cs.o wavelan_cs.c
In file included from wavelan_cs.c:67:
wavelan_cs.h:492:33: warning: extra tokens at end of #undef directive
...
<-- snip -->
The fix is trivial:
--- linux-2.4.21-rc3-modular/drivers/net/pcmcia/wavelan_cs.h.old 2003-05-24 10:38:32.000000000 +0200
+++ linux-2.4.21-rc3-modular/drivers/net/pcmcia/wavelan_cs.h 2003-05-24 10:38:53.000000000 +0200
@@ -489,7 +489,7 @@
#undef DEBUG_RX_INFO /* Header of the transmitted packet */
#undef DEBUG_RX_FAIL /* Normal failure conditions */
#define DEBUG_RX_ERROR /* Unexpected conditions */
-#undef DEBUG_PACKET_DUMP 32 /* Dump packet on the screen */
+#undef DEBUG_PACKET_DUMP /* Dump packet on the screen */
#undef DEBUG_IOCTL_TRACE /* Misc call by Linux */
#undef DEBUG_IOCTL_INFO /* Various debug info */
#define DEBUG_IOCTL_ERROR /* What's going wrong */
I've tested the compilation with 2.4.21-rc3.
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:[~2003-05-24 8:33 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=20030524084605.GD1824@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--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