From: Greg KH <greg@kroah.com>
To: "Ian S. Nelson" <nelcomp@attglobal.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: __FUNCTION__
Date: Tue, 8 Jan 2002 14:17:20 -0800 [thread overview]
Message-ID: <20020108221719.GA15986@kroah.com> (raw)
In-Reply-To: <3C3B664B.3060103@intel.com> <3C3B6BD2.9070201@attglobal.net>
In-Reply-To: <3C3B6BD2.9070201@attglobal.net>
On Tue, Jan 08, 2002 at 02:59:46PM -0700, Ian S. Nelson wrote:
>
> I suspect this might be about as religious an issue as there is but has
> anyone thought about coming up with some "standard" debugging macros,
> perhaps something that can be configured at compile time from the
> configuration for everyone to use everywhere? I've got my own debug
> macros, essentially a printk with the file, function and line added
> wrapped in #ifdef DEBUG. I've seen several other schemes in other parts
> of the kernel and now some of them aren't correct.
Jeff Garzik and others have talked about unifying the network driver's
debug statements and levels with a common set of macros and level
values. I want to do the same thing with the USB drivers, but was
waiting for them to finalize their scheme first (and hopefully use the
same thing.)
So yes, I think there can be some kind of "standard" debugging macros,
but the "standard" will probably be limited to a subset of the kernel.
greg k-h
next prev parent reply other threads:[~2002-01-08 22:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-08 21:36 __FUNCTION__ Vladimir Kondratiev
2002-01-08 21:59 ` __FUNCTION__ Ian S. Nelson
2002-01-08 22:17 ` Greg KH [this message]
2002-01-08 23:09 ` __FUNCTION__ Vladimir Kondratiev
2002-01-08 22:01 ` __FUNCTION__ Greg KH
2002-01-08 22:56 ` __FUNCTION__ jtv
2002-01-08 23:11 ` __FUNCTION__ Greg KH
2002-01-08 23:39 ` __FUNCTION__ David Weinehall
2002-01-08 23:51 ` __FUNCTION__ Andrew Morton
2002-01-09 0:04 ` __FUNCTION__ David Weinehall
2002-01-09 0:14 ` __FUNCTION__ Andrew Morton
2002-01-09 0:23 ` __FUNCTION__ Anton Altaparmakov
2002-01-08 23:42 ` __FUNCTION__ jtv
2002-01-09 2:12 ` __FUNCTION__ Richard Henderson
2002-01-09 7:23 ` __FUNCTION__ Greg KH
2002-01-09 7:32 ` __FUNCTION__ Neil Booth
2002-01-09 22:35 ` __FUNCTION__ Richard Henderson
2002-01-09 9:05 ` __FUNCTION__ Martin Dalecki
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=20020108221719.GA15986@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nelcomp@attglobal.net \
/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.