From: Dmitry Voytik <dvv.kernel@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: David Rientjes <rientjes@google.com>,
linux-kernel@vger.kernel.org,
Dmitry Voytik <dvv.kernel@gmail.com>
Subject: [PATCH] staging: android: lowmemorykiller: well-marked debug print
Date: Sat, 16 Mar 2013 11:37:26 +0400 [thread overview]
Message-ID: <1363419446-21236-1-git-send-email-dvv.kernel@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1303151508070.32475@chino.kir.corp.google.com>
Add "lowmemorykiller:" prefix to the debug print so it's easier to
analyse LMK's debug output:
dmesg | grep lowmemorykiller
Signed-off-by: Dmitry Voytik <dvv.kernel@gmail.com>
---
drivers/staging/android/lowmemorykiller.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/android/lowmemorykiller.c b/drivers/staging/android/lowmemorykiller.c
index 53d80c2..fe74494 100644
--- a/drivers/staging/android/lowmemorykiller.c
+++ b/drivers/staging/android/lowmemorykiller.c
@@ -30,6 +30,8 @@
*
*/
+#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
+
#include <linux/module.h>
#include <linux/kernel.h>
#include <linux/mm.h>
@@ -61,7 +63,7 @@ static unsigned long lowmem_deathpending_timeout;
#define lowmem_print(level, x...) \
do { \
if (lowmem_debug_level >= (level)) \
- printk(x); \
+ pr_info(x); \
} while (0)
static int lowmem_shrink(struct shrinker *s, struct shrink_control *sc)
--
1.7.9.5
prev parent reply other threads:[~2013-03-16 7:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 20:00 [PATCH] staging: android: lowmemorykiller: well-marked debug print Dmitry Voytik
2013-03-15 20:09 ` Greg Kroah-Hartman
2013-03-15 22:08 ` David Rientjes
2013-03-16 7:14 ` Dmitry Voytik
2013-03-16 7:37 ` Dmitry Voytik [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=1363419446-21236-1-git-send-email-dvv.kernel@gmail.com \
--to=dvv.kernel@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.