From: Dave Kleikamp <shaggy@austin.ibm.com>
To: Adrian Bunk <bunk@fs.tum.de>, Andrew Morton <akpm@digeo.com>
Cc: James Lamanna <james.lamanna@appliedminds.com>,
"'Linus Torvalds'" <torvalds@transmeta.com>,
jfs-discussion@www-124.southbury.usf.ibm.com,
"'Kernel Mailing List'" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH - 2.5.60] JFS no longer compiles with gcc 2.95
Date: Wed, 12 Feb 2003 09:42:01 -0600 [thread overview]
Message-ID: <200302120942.01078.shaggy@austin.ibm.com> (raw)
In-Reply-To: <20030212150435.GL17128@fs.tum.de>
On Wednesday 12 February 2003 09:04, Adrian Bunk wrote:
> Ah, then it's a well-known 2.95 parser bug (sorry for not looking
> better at it when sending my initial report). The following
> alternative patch is sufficient to fix the compilation with 2.95
> (it's your choice which of the two patches you prefer):
>
> --- linux-2.5.60-full/fs/jfs/jfs_debug.h.old 2003-02-12
> 15:59:14.000000000 +0100 +++
> linux-2.5.60-full/fs/jfs/jfs_debug.h 2003-02-12 15:59:35.000000000
> +0100 @@ -90,7 +90,7 @@
> #define jfs_err(fmt, arg...) do { \
> if (jfsloglevel >= JFS_LOGLEVEL_ERR) \
> printk(KERN_ERR "%s:%d " fmt "\n", \
> - __FILE__, __LINE__, ## arg); \
> + __FILE__ , __LINE__ , ## arg); \
> } while (0)
>
> /*
Interesting that the assert() macro in the same file is very similar,
but apparently doesn't have the same problem. Do you know if it's tied
to the ## operator? I'm not emotionally attached to __FILE__ and
__LINE__, so I'll just go with removing them, unless anyone wants to
change my mind.
Thanks,
Shaggy
--
David Kleikamp
IBM Linux Technology Center
next prev parent reply other threads:[~2003-02-12 15:32 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-10 19:08 Linux 2.5.60 Linus Torvalds
2003-02-10 20:41 ` Maciej Soltysiak
2003-02-10 21:06 ` Linux 2.5.60 Compile error James Lamanna
2003-02-10 21:38 ` Kevin Corry
2003-02-10 22:50 ` Muli Ben-Yehuda
2003-02-10 21:52 ` Dave Jones
2003-02-11 0:12 ` Another " Vlad@geekizoid.com
2003-02-11 5:21 ` Anthony J. Breeds-Taurima
2003-02-10 21:11 ` Linux 2.5.60 Stephen Hemminger
2003-02-10 21:25 ` James Lamanna
2003-02-10 22:54 ` Linus Torvalds
2003-02-10 20:46 ` 2.5.60: JFS no longer compiles with gcc 2.95 Adrian Bunk
2003-02-10 21:43 ` James Lamanna
2003-02-11 7:27 ` Adrian Bunk
2003-02-12 14:52 ` [PATCH - 2.5.60] " Dave Kleikamp
2003-02-12 15:04 ` Adrian Bunk
2003-02-12 15:42 ` Dave Kleikamp [this message]
2003-02-12 16:22 ` Andreas Schwab
2003-02-10 22:21 ` Linux 2.5.60 John Cherry
2003-02-11 7:08 ` Oleg Drokin
2003-02-11 7:38 ` Linus Torvalds
2003-02-12 8:11 ` Eric W. Biederman
2003-02-12 11:49 ` Jeff Dike
2003-02-13 23:25 ` Werner Almesberger
2003-02-11 15:16 ` Zephaniah E. Hull
2003-02-11 22:47 ` Andrew Morton
2003-02-11 22:54 ` Andrew Morton
2003-02-14 16:56 ` Zephaniah E. Hull
2003-02-11 16:23 ` Russell King
2003-02-11 17:06 ` Linus Torvalds
2003-02-12 2:47 ` David S. Miller
2003-02-11 16:44 ` 2.5.60: arlan.c no longer compiles Adrian Bunk
2003-02-11 23:08 ` Andrew Morton
2003-02-11 18:16 ` 2.5.60: sim710.c doesn't compile Adrian Bunk
2003-02-11 18:21 ` James Bottomley
2003-02-11 22:00 ` Linux 2.5.60 Rudmer van Dijk
2003-02-12 10:05 ` Ingo Oeser
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=200302120942.01078.shaggy@austin.ibm.com \
--to=shaggy@austin.ibm.com \
--cc=akpm@digeo.com \
--cc=bunk@fs.tum.de \
--cc=james.lamanna@appliedminds.com \
--cc=jfs-discussion@www-124.southbury.usf.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®