From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Krzysztof Helt <krzysztof.h1@poczta.fm>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux-fbdev-devel <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [PATCH 1/4] cirrusfb: fix up debug printk types
Date: Sat, 6 Sep 2008 12:41:14 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0809061238360.4138@anakin> (raw)
In-Reply-To: <20080906121353.d6ed31c8.krzysztof.h1@poczta.fm>
On Sat, 6 Sep 2008, Krzysztof Helt wrote:
> On Sat, 6 Sep 2008 10:37:27 +0200 (CEST)
> Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > On Fri, 5 Sep 2008, Krzysztof Helt wrote:
> > > From: Krzysztof Helt <krzysztof.h1@wp.pl>
> > >
> > > Fix debug printk types mismatch after
> > > my earlier changes.
> >
> > #define DPRINTK(fmt, args...) pr_debug("%s: " fmt, __func__ , ## args)
> >
> > unconditionally, so you always catch these?
> >
>
> I do not understand. Is it a suggestion to make DPRINTK unconditional?
Yes.
> Then, the amount of information printed should be trimmed down. It is excessive now.
Please not that pr_debug() gets optimized away if DEBUG is not defined
( i.e. it doesn't cause excessive output), while it still performs
printf()-style format checking.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
next prev parent reply other threads:[~2008-09-06 10:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-05 21:53 [PATCH 1/4] cirrusfb: fix up debug printk types Krzysztof Helt
2008-09-06 8:37 ` Geert Uytterhoeven
2008-09-06 10:13 ` Krzysztof Helt
2008-09-06 10:41 ` Geert Uytterhoeven [this message]
2008-10-15 23:05 ` Andrew Morton
2008-10-23 18:24 ` Krzysztof Helt
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=Pine.LNX.4.64.0809061238360.4138@anakin \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=krzysztof.h1@poczta.fm \
--cc=linux-fbdev-devel@lists.sourceforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox