From: Andreas Steinmetz <ast@domdv.de>
To: Ahmed Masud <masud@googgun.com>
Cc: Thunder from the hill <thunder@lightweight.ods.org>,
dag@brattli.net, linux-kernel@vger.kernel.org
Subject: Re: 2.5.34: IR __FUNCTION__ breakage
Date: Fri, 13 Sep 2002 20:01:14 +0200 [thread overview]
Message-ID: <3D8227EA.6040708@domdv.de> (raw)
In-Reply-To: 3D82247A.80601@googgun.com
(rct@gherkin.frus.com removed from cc list as his mta treats (not only)
my mails as spam...)
Ahmed Masud wrote:
> Thunder from the hill wrote:
>
>> Hi,
>>
>> On Fri, 13 Sep 2002, Andreas Steinmetz wrote:
>>
>>> At least for gcc 3.2 this would be better:
>>>
>>> #define DERROR(dbg, fmt, args...) \
>>> do { if (DEBUG_##dbg) \
>>> printk(KERN_INFO "irnet: %s(): " fmt, __FUNCTION__, ##args); \
>>> } while(0)
>>>
> Perhaps a hybrid of the two? :
>
> #define DERROR(dbg, fmt,
> args...) \
> do { if (DEBUG_##dbg) { \
> printk(KERN_INFO "irnet: %s() : ", __FUNCTION__); \
> printk(fmt, ## args); \
> } \
> } while (0)
>
>
How about what I did just suggest for smbfs?
#if __GNUC__>=3
#define DERROR(dbg, fmt, args...) \
do { if (DEBUG_##dbg) \
printk(KERN_INFO "irnet: %s(): " fmt, __FUNCTION__, ##args); \
} while(0)
#else
#define DERROR(dbg, args...) \
{if(DEBUG_##dbg) \
printk(KERN_INFO "irnet: " __FUNCTION__ "(): " args);}
#endif
gcc 2 versions will be deprecated eventually some time in the future and
in between the macro selection by gcc major version should be fair enough.
--
Andreas Steinmetz
D.O.M. Datenverarbeitung GmbH
next prev parent reply other threads:[~2002-09-13 17:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 19:54 2.5.34: IR __FUNCTION__ breakage Bob_Tracy
2002-09-12 20:16 ` Thunder from the hill
2002-09-12 21:09 ` Bob_Tracy
2002-09-13 16:01 ` Andreas Steinmetz
2002-09-13 16:14 ` Thunder from the hill
2002-09-13 17:46 ` Ahmed Masud
2002-09-13 18:01 ` Andreas Steinmetz [this message]
2002-09-13 20:11 ` Thunder from the hill
2002-09-13 20:12 ` Neil Booth
2002-09-13 20:30 ` Andreas Steinmetz
2002-09-13 20:53 ` Thunder from the hill
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=3D8227EA.6040708@domdv.de \
--to=ast@domdv.de \
--cc=dag@brattli.net \
--cc=linux-kernel@vger.kernel.org \
--cc=masud@googgun.com \
--cc=thunder@lightweight.ods.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