From: <zhe.he@windriver.com>
To: akpm@linux-foundation.org, mhocko@suse.com, vbabka@suse.cz,
pasha.tatashin@oracle.com, mgorman@techsingularity.net,
aaron.lu@intel.com, osalvador@suse.de, iamjoonsoo.kim@lge.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
zhe.he@windriver.com
Subject: [PATCH v2 2/2] mm/page_alloc: Add KBUILD_MODNAME
Date: Sat, 22 Sep 2018 22:53:33 +0800 [thread overview]
Message-ID: <1537628013-243902-2-git-send-email-zhe.he@windriver.com> (raw)
In-Reply-To: <1537628013-243902-1-git-send-email-zhe.he@windriver.com>
From: He Zhe <zhe.he@windriver.com>
Add KBUILD_MODNAME to make prints more clear.
Signed-off-by: He Zhe <zhe.he@windriver.com>
Cc: akpm@linux-foundation.org
Cc: mhocko@suse.com
Cc: vbabka@suse.cz
Cc: pasha.tatashin@oracle.com
Cc: mgorman@techsingularity.net
Cc: aaron.lu@intel.com
Cc: osalvador@suse.de
Cc: iamjoonsoo.kim@lge.com
---
v2:
Split the addition of KBUILD_MODNAME out
mm/page_alloc.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index f34cae1..ead9556 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -14,6 +14,8 @@
* (lots of bits borrowed from Ingo Molnar & Andrew Morton)
*/
+#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
+
#include <linux/stddef.h>
#include <linux/mm.h>
#include <linux/swap.h>
--
2.7.4
next prev parent reply other threads:[~2018-09-22 14:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-22 14:53 [PATCH v2 1/2] mm/page_alloc: Fix panic caused by passing debug_guardpage_minorder or kernelcore to command line zhe.he
2018-09-22 14:53 ` zhe.he [this message]
2018-09-24 14:26 ` [PATCH v2 2/2] mm/page_alloc: Add KBUILD_MODNAME Michal Hocko
2018-09-24 14:24 ` [PATCH v2 1/2] mm/page_alloc: Fix panic caused by passing debug_guardpage_minorder or kernelcore to command line Michal Hocko
2018-09-24 21:42 ` Andrew Morton
2018-09-25 5:59 ` Michal Hocko
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=1537628013-243902-2-git-send-email-zhe.he@windriver.com \
--to=zhe.he@windriver.com \
--cc=aaron.lu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=osalvador@suse.de \
--cc=pasha.tatashin@oracle.com \
--cc=vbabka@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).