mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Erik McKee <camhanaich99@yahoo.com>
To: Urban Widmark <urban@teststation.com>
Cc: linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@transmeta.com>,
	kernel-newbies@vger.kernel.org, davej@suse.de,
	Adrian Bunk <bunk@fs.tum.de>
Subject: Re: [ERROR][PATCH] smbfs compilation in 2.5.21
Date: Sun, 16 Jun 2002 09:24:02 -0700 (PDT)	[thread overview]
Message-ID: <20020616162402.32079.qmail@web14201.mail.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0206161257390.5774-100000@cola.enlightnet.local>

THis is from the bk tree.  It's gcc 2.95.3.  That solution might be a bettr one
after all ;)  However, would the stringifying done here to get the function
name in there mess that up?

Erik McKee


--- Urban Widmark <urban@teststation.com> wrote:
> On Sat, 15 Jun 2002, Erik McKee wrote:
> 
> > diff -Nru a/fs/smbfs/smb_debug.h b/fs/smbfs/smb_debug.h
> > --- a/fs/smbfs/smb_debug.h	Sat Jun 15 23:12:04 2002
> > +++ b/fs/smbfs/smb_debug.h	Sat Jun 15 23:12:04 2002
> > @@ -12,8 +12,10 @@
> >   */
> >  #ifdef SMBFS_PARANOIA
> >  # define PARANOIA(f, a...) printk(KERN_NOTICE "%s: " f, __FUNCTION__, ##
> a)
> > +# define PARANOIA2(f) printk(KERN_NOTICE "%s: "f, __FUNCTION__)
> 
> Are you looking at BK, the 2.5.21 tree I'm looking at still has:
> #define PARANOIA(x...) printk(KERN_NOTICE __FUNCTION__ ": " x)
> 
> I assume you are using gcc 3.x? (which one?)
> I don't get any warnings/errors on 2.96.
> 
> 
> I think having two macros for exactly the same thing is ugly. A better
> solution might be to borrow some code from arch/ia64/kernel/unaligned.c
> 
> #define PARANOIA(f...) \
> 	do { printk(KERN_NOTICE "%s: ", __FUNCTION__); printk(f); } while(0)
> 
> (untested, and I think this will print an extra "<4>" ?)
> Unless someone has a better idea. In any case, the other printk macros in
> smb_debug.h needs treatment too and not just the PARANOIA macro.
> 
> 
> If you are cleaning things up I think that the following also sometimes
> use debug macros with a single string, but with a 'macro(a, b...)' syntax:
> 
> drivers/net/pci-skeleton.c
> drivers/char/i810_rng.c
> sound/oss/via82cxxx_audio.c
> 	DPRINTK
> 
> drivers/hotplug/pci_hotplug_{core,util}.c
> 	dbg/err/info/warn
> 
> drivers/char/machzwd.c
> 	dprnintk
> 
> drivers/ieee1394/sbp2.c
> 	SBP2_ORB_DEBUG
> 
> net/ipv4/netfilter/ipt_ULOG.c
> net/ipv4/netfilter/ip_conntrack_irc.c
> 	DEBUGP
> 
> sound/oss/vwsnd.c
> 	DBGP
> 
> fs/ntfs/debug.h
> 	ntfs_warning/ntfs_error
> 
> 
> Many of them are not enabled by default, and maybe they have already been
> taken care of.
> 
> And maybe run suggested changes by the respective maintainers first.
> Thanks.
> 
> /Urban
> 


__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

  reply	other threads:[~2002-06-16 16:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-16  4:28 Erik McKee
2002-06-16 12:59 ` Urban Widmark
2002-06-16 16:24   ` Erik McKee [this message]
2002-06-16 17:13     ` Urban Widmark
2002-06-16 18:26   ` Linus Torvalds
2002-06-16 18:40     ` Urban Widmark

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=20020616162402.32079.qmail@web14201.mail.yahoo.com \
    --to=camhanaich99@yahoo.com \
    --cc=bunk@fs.tum.de \
    --cc=davej@suse.de \
    --cc=kernel-newbies@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=urban@teststation.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®