From: Daniel Bristot de Oliveira <bristot@redhat.com>
To: Colin King <colin.king@canonical.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] trace: Fix spelling in osnoise tracer "interferences" -> "interference"
Date: Mon, 28 Jun 2021 15:14:34 +0200 [thread overview]
Message-ID: <e53ec856-c93d-61fe-ec2f-6c73b3b6efc9@redhat.com> (raw)
In-Reply-To: <20210628125522.56361-1-colin.king@canonical.com>
On 6/28/21 2:55 PM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> There is a spelling mistake in a TP_printk message, the word interferences
> is not the plural of interference. Fix this.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Reviewed-by: Daniel Bristot de Oliveira <bristot@redhat.com>
Thanks!
-- Daniel
> ---
> include/trace/events/osnoise.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/trace/events/osnoise.h b/include/trace/events/osnoise.h
> index 28762c69f6c9..82f741ec0f57 100644
> --- a/include/trace/events/osnoise.h
> +++ b/include/trace/events/osnoise.h
> @@ -129,7 +129,7 @@ TRACE_EVENT(sample_threshold,
> __entry->interference = interference;
> ),
>
> - TP_printk("start %llu.%09u duration %llu ns interferences %llu",
> + TP_printk("start %llu.%09u duration %llu ns interference %llu",
> __print_ns_to_secs(__entry->start),
> __print_ns_without_secs(__entry->start),
> __entry->duration,
>
prev parent reply other threads:[~2021-06-28 13:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 12:55 [PATCH][next] trace: Fix spelling in osnoise tracer "interferences" -> "interference" Colin King
2021-06-28 13:14 ` Daniel Bristot de Oliveira [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=e53ec856-c93d-61fe-ec2f-6c73b3b6efc9@redhat.com \
--to=bristot@redhat.com \
--cc=colin.king@canonical.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.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