From: Daniele Pizzoni <auouo@tin.it>
To: Ingo Molnar <mingo@elte.hu>
Cc: kernel-janitors <kernel-janitors@lists.osdl.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/8] replacing/fixing printk with pr_debug/pr_info in arch/i386 - intro
Date: Mon, 18 Oct 2004 14:59:44 +0200 [thread overview]
Message-ID: <1098104383.3024.44.camel@pdp11.tsho.org> (raw)
In-Reply-To: <20041018103633.GA6792@elte.hu>
On lun, 2004-10-18 at 12:36, Ingo Molnar wrote:
>
> ok - pr_debug() is ok i think for the APIC code. It pairs well with the
> other variants: pr_notice(), etc.
> [...]
> i'd suggest to first do the Dprintk -> pr_debug replacement patch with
> as few output changes as possible. (output changes are unavoidable when
> converting a \n-less printout.) Then do any format cleanups in a
> separate patch.
Look, there is no pr_notice at all. The whole thing is not very clear I
think, and the pr_ macros have some problem.
This is the kernel.h part regarding the two and only pr_debug and
pr_info:
#ifdef DEBUG
#define pr_debug(fmt,arg...) \
printk(KERN_DEBUG fmt,##arg)
#else
#define pr_debug(fmt,arg...) \
do { } while (0)
#endif
#define pr_info(fmt,arg...) \
printk(KERN_INFO fmt,##arg)
I think that pr_debug does make sense, because it depends on DEBUG and
is a useful macro uniforming all the DPRINTK usage.
pr_info is alone, there are no other pr_*. I used it in the patches but
now I think I was wrong. You cannot "continue" a pr_info as you do with
printk because it always inserts the loglevel tag. I think it's better
not use it or find a better solution. In fact it is not used too much in
the kernel.
I'll try some strict dprintk -> pr_debug replacements.
Bye
Daniele
next prev parent reply other threads:[~2004-10-18 11:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-17 17:10 Daniele Pizzoni
2004-10-17 16:19 ` Ingo Molnar
2004-10-17 18:10 ` Geert Uytterhoeven
2004-10-17 18:23 ` Joe Perches
2004-10-17 18:34 ` Geert Uytterhoeven
2004-10-18 2:41 ` Daniele Pizzoni
2004-10-18 10:36 ` Ingo Molnar
2004-10-18 12:59 ` Daniele Pizzoni [this message]
[not found] <2QlVm-7u4-13@gated-at.bofh.it>
[not found] ` <2Qmok-7KK-1@gated-at.bofh.it>
2004-10-17 20:26 ` Andi Kleen
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=1098104383.3024.44.camel@pdp11.tsho.org \
--to=auouo@tin.it \
--cc=kernel-janitors@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®