linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: rct@gherkin.frus.com (Bob_Tracy)
To: Thunder from the hill <thunder@lightweight.ods.org>
Cc: dag@brattli.net, linux-kernel@vger.kernel.org
Subject: Re: 2.5.34: IR __FUNCTION__ breakage
Date: Thu, 12 Sep 2002 16:09:40 -0500 (CDT)	[thread overview]
Message-ID: <m17pbDY-0005khC@gherkin.frus.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0209121414570.10048-100000@hawkeye.luckynet.adm> "from Thunder from the hill at Sep 12, 2002 02:16:49 pm"

Thunder from the hill wrote:
> (good suggestion)

so the revised definition expands from two+ to three+ arguments and
becomes

#define DERROR(dbg, fmt, args...) \
    {if(DEBUG_##dbg) \
    	printk(KERN_INFO "irnet: %s(): " fmt, __FUNCTION__, args);}

in the style of the original code.  There aren't all that many source
files that depend on irnet.h, so this shouldn't be too painful.

TO DO: under linux/net/irda, there's a *lot* of cli(), restore_flags(),
save_flags() cleanup work, which I'll happily leave to Jean and/or
Dag :-).

-- 
-----------------------------------------------------------------------
Bob Tracy                   WTO + WIPO = DMCA? http://www.anti-dmca.org
rct@frus.com
-----------------------------------------------------------------------

  reply	other threads:[~2002-09-12 21:05 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 [this message]
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
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=m17pbDY-0005khC@gherkin.frus.com \
    --to=rct@gherkin.frus.com \
    --cc=dag@brattli.net \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).