From: Pete <greg.petr@gmail.com>
To: Matthew Wilcox <matthew@wil.cx>, Joe Perches <joe@perches.com>
Cc: kernel-janitors@vger.kernel.org, trivial@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs: added KERNEL-DEBUG flag to printk statments
Date: Mon, 05 Oct 2009 23:19:12 +0530 [thread overview]
Message-ID: <1254764952.5279.60.camel@linux-k65f.site> (raw)
In-Reply-To: <20091005170903.GA9791@parisc-linux.org>
> Pay special attention to getting DEBUG set in the right place, and
> _at least_ compile-test your code, with and without DEBUG enabled.
> You should really run your code (again, with and without DEBUG enabled)
> and check that it does the right thing.
ok - Thanks will redo, test and send a more generalized version of the
patch which modifies the macro instead.
-Greg
prev parent reply other threads:[~2009-10-05 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 14:43 [PATCH] fs: added KERNEL-DEBUG flag to printk statments Pete
2009-10-05 15:24 ` Pete
2009-10-05 17:09 ` Matthew Wilcox
2009-10-05 17:49 ` Pete [this message]
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=1254764952.5279.60.camel@linux-k65f.site \
--to=greg.petr@gmail.com \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=trivial@kernel.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