From: SeongJae Park <sj38.park@gmail.com>
To: paulmck@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org, SeongJae Park <sj38.park@gmail.com>
Subject: [PATCH 3/3] torture: TOROUT_STRING(): Insert a space between flag and message
Date: Sun, 21 Aug 2016 16:54:40 +0900 [thread overview]
Message-ID: <1471766080-17501-3-git-send-email-sj38.park@gmail.com> (raw)
In-Reply-To: <1471766080-17501-1-git-send-email-sj38.park@gmail.com>
TOROUT_STRING() macro function does not insert a space between flag and
message while other similar couterparts do. The output will be
inconsistent and weird especially when it is read by dmesg with color
option enabled. This commit adds an space between flag and message in
TOROUT_STRING() output.
Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
include/linux/torture.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/torture.h b/include/linux/torture.h
index 6685a73..a45702e 100644
--- a/include/linux/torture.h
+++ b/include/linux/torture.h
@@ -43,7 +43,7 @@
#define TORTURE_FLAG "-torture:"
#define TOROUT_STRING(s) \
- pr_alert("%s" TORTURE_FLAG s "\n", torture_type)
+ pr_alert("%s" TORTURE_FLAG " %s\n", torture_type, s)
#define VERBOSE_TOROUT_STRING(s) \
do { if (verbose) pr_alert("%s" TORTURE_FLAG " %s\n", torture_type, s); } while (0)
#define VERBOSE_TOROUT_ERRSTRING(s) \
--
1.9.1
next prev parent reply other threads:[~2016-08-21 7:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-21 7:54 [PATCH 1/3] rcuperf: Remove unnecessary rcu_perf_writer_state variable SeongJae Park
2016-08-21 7:54 ` [PATCH 2/3] rcuperf: Insert space between flag and message consistently SeongJae Park
2016-08-21 7:54 ` SeongJae Park [this message]
2016-08-21 23:00 ` [PATCH 1/3] rcuperf: Remove unnecessary rcu_perf_writer_state variable Paul E. McKenney
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=1471766080-17501-3-git-send-email-sj38.park@gmail.com \
--to=sj38.park@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox