From: Joe Perches <joe@perches.com>
To: Colin King <colin.king@canonical.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing/syscalls: add in missing white space in error message text
Date: Mon, 12 Sep 2016 10:34:23 -0700 [thread overview]
Message-ID: <1473701663.11006.19.camel@perches.com> (raw)
In-Reply-To: <20160912114127.30980-1-colin.king@canonical.com>
On Mon, 2016-09-12 at 12:41 +0100, Colin King wrote:
> pr_info message spans two lines and the literal string is missing
> a white space between words. Add the white space.
Perhaps better would be to coalesce the format string fragments.
And if you didn't already know, checkpatch can find potential
defects like this using --types=split_string,missing_space
For instance:
$ ./scripts/checkpatch.pl --show-types --types=split_string,missing_space --terse --no-summary \
-f kernel/trace/trace_syscalls.c
kernel/trace/trace_syscalls.c:614: WARNING:SPLIT_STRING: quoted string split across lines
kernel/trace/trace_syscalls.c:614: WARNING:MISSING_SPACE: break quoted strings at a space character
kernel/trace/trace_syscalls.c:686: WARNING:SPLIT_STRING: quoted string split across lines
kernel/trace/trace_syscalls.c:686: WARNING:MISSING_SPACE: break quoted strings at a space character
> diff --git a/kernel/trace/trace_syscalls.c b/kernel/trace/trace_syscalls.c
[]
> @@ -610,7 +610,7 @@ static int perf_sysenter_enable(struct trace_event_call *call)
> if (!sys_perf_refcount_enter)
> ret = register_trace_sys_enter(perf_syscall_enter, NULL);
> if (ret) {
> - pr_info("event trace: Could not activate"
> + pr_info("event trace: Could not activate "
> "syscall entry trace point");
> } else {
> set_bit(num, enabled_perf_enter_syscalls);
> @@ -682,7 +682,7 @@ static int perf_sysexit_enable(struct trace_event_call *call)
> if (!sys_perf_refcount_exit)
> ret = register_trace_sys_exit(perf_syscall_exit, NULL);
> if (ret) {
> - pr_info("event trace: Could not activate"
> + pr_info("event trace: Could not activate "
> "syscall exit trace point");
> } else {
> set_bit(num, enabled_perf_exit_syscalls);
prev parent reply other threads:[~2016-09-12 17:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 11:41 [PATCH] tracing/syscalls: add in missing white space in error message text Colin King
2016-09-12 13:43 ` Steven Rostedt
2016-09-13 18:35 ` Ingo Molnar
2016-09-12 17:34 ` Joe Perches [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=1473701663.11006.19.camel@perches.com \
--to=joe@perches.com \
--cc=colin.king@canonical.com \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).