public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: flaniganr@intel.co.jp
Cc: linux-kernel@vger.kernel.org, jt@hpl.hp.com, dhinds@zen.stanford.edu
Subject: Re: [PATCH] 2.5.8-pre1 wavelan_cs
Date: 04 Apr 2002 02:11:33 -0500	[thread overview]
Message-ID: <1017904326.22304.458.camel@phantasy> (raw)
In-Reply-To: <87vgb8x8bt.fsf@hazuki.jp.intel.com>

On Thu, 2002-04-04 at 01:54, flaniganr@intel.co.jp wrote:

> wavelan_cs.p.h:495:33: warning: extra tokens at end of #undef directive

Good ... and the attached patch will fix the warning wrt trailing tokens
after the undef.

	Robert Love

diff -urN linux-2.5.8-pre1/drivers/net/wireless/wavelan_cs.p.h linux/drivers/net/wireless/wavelan_cs.p.h
--- linux-2.5.8-pre1/drivers/net/wireless/wavelan_cs.p.h	Wed Apr  3 20:57:23 2002
+++ linux/drivers/net/wireless/wavelan_cs.p.h	Thu Apr  4 02:06:49 2002
@@ -492,7 +492,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 */


  reply	other threads:[~2002-04-04  7:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-04  6:54 [PATCH] 2.5.8-pre1 wavelan_cs flaniganr
2002-04-04  7:11 ` Robert Love [this message]
2002-04-04  7:18 ` Jeff Garzik
2002-04-04 17:40   ` Jean Tourrilhes
2002-04-04 19:25     ` Jeff Garzik

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=1017904326.22304.458.camel@phantasy \
    --to=rml@tech9.net \
    --cc=dhinds@zen.stanford.edu \
    --cc=flaniganr@intel.co.jp \
    --cc=jt@hpl.hp.com \
    --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