From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
To: Linus Torvalds <torvalds@transmeta.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Fwd: [PATCH_] Should fix __FUNCTION__ glomming issues with some GCCs
Date: Thu, 3 Oct 2002 09:06:45 +0200 [thread overview]
Message-ID: <20021003090645.A15874@bitwizard.nl> (raw)
Hi Linus,
Approved by author....
Roger.
----- Forwarded message from John R R Leavitt <jrrl@tiki.livetide.com> -----
From: John R R Leavitt <jrrl@tiki.livetide.com>
To: R.E.Wolff@BitWizard.nl
Date: Wed, 2 Oct 2002 22:35:30 -0400
Subject: [PATCH_] Should fix __FUNCTION__ glomming issues with some GCCs
Just wandered the driver tree and fixed these where I could. Here's yours.
-John.
John Leavitt - jrrl@steampunk.com - Linux Consulting
diff -ruN linux-2.5.40-original/drivers/atm/firestream.c linux-2.5.40/drivers/atm/firestream.c
--- linux-2.5.40-original/drivers/atm/firestream.c Tue Oct 1 03:06:18 2002
+++ linux-2.5.40/drivers/atm/firestream.c Wed Oct 2 19:20:13 2002
@@ -330,8 +330,8 @@
#define FS_DEBUG_QSIZE 0x00001000
-#define func_enter() fs_dprintk (FS_DEBUG_FLOW, "fs: enter " __FUNCTION__ "\n")
-#define func_exit() fs_dprintk (FS_DEBUG_FLOW, "fs: exit " __FUNCTION__ "\n")
+#define func_enter() fs_dprintk (FS_DEBUG_FLOW, "fs: enter %s\n", __FUNCTION__)
+#define func_exit() fs_dprintk (FS_DEBUG_FLOW, "fs: exit %s\n", __FUNCTION__)
struct fs_dev *fs_boards = NULL;
----- End forwarded message -----
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* The Worlds Ecosystem is a stable system. Stable systems may experience *
* excursions from the stable situation. We are currenly in such an *
* excursion: The stable situation does not include humans. ***************
reply other threads:[~2002-10-03 7:01 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=20021003090645.A15874@bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.