From: Pete <greg.petr@gmail.com>
To: kernel-janitors@vger.kernel.org, trivial@kernel.org
Cc: Matthew Wilcox <matthew@wil.cx>, Joe Perches <joe@perches.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 1/1, revised] fs: added KERN-DEBUG flag to dprintk macro
Date: Mon, 05 Oct 2009 23:35:15 +0530 [thread overview]
Message-ID: <1254765915.5279.77.camel@linux-k65f.site> (raw)
Signed-off-by: Greg Petr <greg.petr@gmail.com>
Hi,
The following is a trivial patch which adds KERN_DEBUG flag to the
dprintk macro. Made this a more generalized version.
--- linux-2.6/fs/aio.c 2009-10-05 14:46:11.000000000 +0530
+++ linux-2.6.test/fs/aio.c 2009-10-05 23:30:26.000000000 +0530
@@ -37,7 +37,7 @@
#include <asm/uaccess.h>
#if DEBUG > 1
-#define dprintk printk
+#define dprintk(x...) printk(KERN_DEBUG x)
#else
#define dprintk(x...) do { ; } while (0)
#endif
@@ -530,7 +530,7 @@ static void aio_fput_routine(struct work
*/
static int __aio_put_req(struct kioctx *ctx, struct kiocb *req)
{
- dprintk(KERN_DEBUG "aio_put(%p): f_count=%ld\n",
+ dprintk("aio_put(%p): f_count=%ld\n",
req, atomic_long_read(&req->ki_filp->f_count));
assert_spin_locked(&ctx->ctx_lock);
reply other threads:[~2009-10-05 18:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1254765915.5279.77.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