From: Nick Andrew <nick@nick-andrew.net>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
davem@davemloft.net
Subject: Re: [LMB][1/2] Fix some whitespace and other formatting issues, use pr_debug
Date: Sun, 13 Apr 2008 02:29:40 +1000 [thread overview]
Message-ID: <20080412162940.GB29599@tull.net> (raw)
In-Reply-To: <18432.18107.29491.115996@cargo.ozlabs.ibm.com>
On Sat, Apr 12, 2008 at 03:20:59PM +1000, Paul Mackerras wrote:
> + pr_debug("\n reserved.cnt = 0x%lx\n", lmb.reserved.cnt);
This will only output an empty line at KERN_DEBUG level and the rest
will be at default_message_loglevel. Problem is fixed my my patch in msg
<20080412161733.24882.30930.stgit@marcab.local.tull.net>
However, is a blank line in the log necessary?
Nick.
next prev parent reply other threads:[~2008-04-12 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-12 5:20 [LMB][1/2] Fix some whitespace and other formatting issues, use pr_debug Paul Mackerras
2008-04-12 16:29 ` Nick Andrew [this message]
2008-04-13 12:31 ` Paul Mackerras
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=20080412162940.GB29599@tull.net \
--to=nick@nick-andrew.net \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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