From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Colin King <colin.king@canonical.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] perf trace: use correct SECCOMP prefix spelling, "SECOMP_*" -> "SECCOMP_*"
Date: Fri, 21 Dec 2018 12:46:11 +0000 [thread overview]
Message-ID: <20181221124611.GA4210@kernel.org> (raw)
In-Reply-To: <20181221084809.6108-1-colin.king@canonical.com>
Em Fri, Dec 21, 2018 at 08:48:09AM +0000, Colin King escreveu:
> From: Colin Ian King <colin.king@canonical.com>
>
> The spelling of the SECCOMP is incorrect, fix these.
Thanks, applied.
- Arnaldo
> Fixes: c65c83ffe904 ("perf trace: Allow asking for not suppressing common string prefixes")
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> tools/perf/trace/beauty/seccomp.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tools/perf/trace/beauty/seccomp.c b/tools/perf/trace/beauty/seccomp.c
> index 4600c28a3cfe..637722e2796b 100644
> --- a/tools/perf/trace/beauty/seccomp.c
> +++ b/tools/perf/trace/beauty/seccomp.c
> @@ -9,7 +9,7 @@
> static size_t syscall_arg__scnprintf_seccomp_op(char *bf, size_t size, struct syscall_arg *arg)
> {
> bool show_prefix = arg->show_string_prefix;
> - const char *prefix = "SECOMP_SET_MODE_";
> + const char *prefix = "SECCOMP_SET_MODE_";
> int op = arg->val;
> size_t printed = 0;
>
> @@ -34,7 +34,7 @@ static size_t syscall_arg__scnprintf_seccomp_flags(char *bf, size_t size,
> struct syscall_arg *arg)
> {
> bool show_prefix = arg->show_string_prefix;
> - const char *prefix = "SECOMP_FILTER_FLAG_";
> + const char *prefix = "SECCOMP_FILTER_FLAG_";
> int printed = 0, flags = arg->val;
>
> #define P_FLAG(n) \
> --
> 2.19.1
--
- Arnaldo
prev parent reply other threads:[~2018-12-21 12:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 8:48 [PATCH][next] perf trace: use correct SECCOMP prefix spelling, "SECOMP_*" -> "SECCOMP_*" Colin King
2018-12-21 12:46 ` Arnaldo Carvalho de Melo [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=20181221124611.GA4210@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=colin.king@canonical.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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