From: Arnd Bergmann <arnd@arndb.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [Kernel-janitors] [PATCH 2/5] Remove concatenation with
Date: Tue, 23 Mar 2004 18:40:20 +0000 [thread overview]
Message-ID: <200403231940.21045.arnd@arndb.de> (raw)
In-Reply-To: <20040322052155.GF17221@bakeyournoodle.com>
On Monday 22 March 2004 06:35, Tony Breeds wrote:
> @@ -70,8 +70,8 @@ typedef enum {
> #define TRACE(l, m, i...) \
> { \
> if ((ft_trace_t)(l) = FT_TRACE_TOP_LEVEL) { \
> - printk(KERN_INFO"ftape"__FILE__"("__FUNCTION__"):\n" \
> - KERN_INFO m".\n" ,##i); \
> + printk(KERN_INFO"ftape%s(%s):\n" \
> + KERN_INFO m".\n" ,__FILE__, __FUNCTION__, ##i); \
Old gcc versions (gcc-2.95 and earlier) require you to have a space in
front of the ', ##', for obscure reasons. OTOH, you should use normal
spacing rules for all other occurrences of ','.
The correct line should look like:
+ KERN_INFO m".\n", __FILE__, __FUNCTION__ , ##i); \
> --- linux-2.6.4.clean/drivers/media/video/w9966.c 2004-03-19 15:52:37.000000000 +1100
> +++ linux-2.6.4.kj_func/drivers/media/video/w9966.c 2004-03-22 11:53:14.000000000 +1100
> @@ -63,7 +63,7 @@
> //#define DEBUG // Undef me for production
>
> #ifdef DEBUG
> -#define DPRINTF(x, a...) printk(KERN_DEBUG "W9966: "__FUNCTION__ "(): "x, ##a)
> +#define DPRINTF(x, a...) printk(KERN_DEBUG "W9966: %s(): "x, __FUNCTION__, ##a)
> #else
This was already broken, but you can fix it while you are at it.
Your other patches have more examples similar to these two. I wonder if
we should make broken varargs macros a new janitor item or just fix those
that cause trouble and deprecate gcc-2.x for linux-2.7.
Arnd <><
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2004-03-23 18:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-22 5:35 [Kernel-janitors] [PATCH 2/5] Remove concatenation with Tony Breeds
2004-03-23 18:40 ` Arnd Bergmann [this message]
2004-03-27 5:06 ` [Kernel-janitors] [PATCH 0/5] remove " Tony Breeds
2004-03-27 5:11 ` [Kernel-janitors] [PATCH 1/5] " Tony Breeds
2004-03-27 5:12 ` [Kernel-janitors] [PATCH 0/5] " Tony Breeds
2004-03-27 5:12 ` Tony Breeds
2004-03-27 5:13 ` [Kernel-janitors] [PATCH 4/5] " Tony Breeds
2004-03-27 5:17 ` [Kernel-janitors] [PATCH 5/5] " Tony Breeds
2004-04-01 21:55 ` Randy.Dunlap
2004-04-01 22:24 ` Tony Breeds
2004-04-01 23:00 ` Randy.Dunlap
2004-04-02 0:35 ` Randy.Dunlap
2004-04-04 2:20 ` Tony Breeds
2004-04-04 2:28 ` Randy.Dunlap
2004-04-04 3:16 ` [Kernel-janitors] [PATCH 2/5] " Tony Breeds
2004-04-04 3:16 ` [Kernel-janitors] [PATCH 4/5] " Tony Breeds
2004-04-04 3:16 ` [Kernel-janitors] [PATCH 1/5] " Tony Breeds
2004-04-04 3:16 ` [Kernel-janitors] [PATCH 0/5] " Tony Breeds
2004-04-04 3:16 ` [Kernel-janitors] [PATCH 5/5] " Tony Breeds
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=200403231940.21045.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=kernel-janitors@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 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.