From: Steven Rostedt <rostedt@goodmis.org>
To: Jesper Dangaard Brouer <brouer@redhat.com>
Cc: linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH] tracing: spelling fixes for CONFIG_HWLAT_TRACER
Date: Mon, 31 Oct 2016 11:09:31 -0400 [thread overview]
Message-ID: <20161031110931.44da91ff@grimm.local.home> (raw)
In-Reply-To: <20161031100828.19656.33026.stgit@firesoul>
On Mon, 31 Oct 2016 11:08:28 +0100
Jesper Dangaard Brouer <brouer@redhat.com> wrote:
> Trivial spelling fixes for Kconfig help text of config HWLAT_TRACER.
>
> Fixes: e7c15cd8a113 ("tracing: Added hardware latency tracer")
> Signed-off-by: Jesper Dangaard Brouer <brouer@redhat.com>
Acked-by: Steven Rostedt <rostedt@goodmis.org>
-- Steve
> ---
> kernel/trace/Kconfig | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
> index 2a96b063d659..fd241ef8febe 100644
> --- a/kernel/trace/Kconfig
> +++ b/kernel/trace/Kconfig
> @@ -221,7 +221,7 @@ config HWLAT_TRACER
> select GENERIC_TRACER
> help
> This tracer, when enabled will create one or more kernel threads,
> - depening on what the cpumask file is set to, which each thread
> + depending on what the cpumask file is set to, which each thread
> spinning in a loop looking for interruptions caused by
> something other than the kernel. For example, if a
> System Management Interrupt (SMI) takes a noticeable amount of
> @@ -236,7 +236,7 @@ config HWLAT_TRACER
> iteration
>
> A kernel thread is created that will spin with interrupts disabled
> - for "width" microseconds in every "widow" cycle. It will not spin
> + for "width" microseconds in every "window" cycle. It will not spin
> for "window - width" microseconds, where the system can
> continue to operate.
>
next prev parent reply other threads:[~2016-10-31 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 10:08 [PATCH] tracing: spelling fixes for CONFIG_HWLAT_TRACER Jesper Dangaard Brouer
2016-10-31 15:09 ` Steven Rostedt [this message]
2016-11-07 15:46 ` Steven Rostedt
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=20161031110931.44da91ff@grimm.local.home \
--to=rostedt@goodmis.org \
--cc=brouer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@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