linux-kernel - Re: [PATCH] tracing: spelling fixes for CONFIG_HWLAT

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20161107104609.4cee0a41@gandalf.local.home>
Date:   Mon, 7 Nov 2016 10:46:09 -0500
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Jesper Dangaard Brouer <brouer@...hat.com>
Cc:     linux-kernel@...r.kernel.org, trivial@...nel.org
Subject: Re: [PATCH] tracing: spelling fixes for CONFIG_HWLAT_TRACER

On Mon, 31 Oct 2016 11:08:28 +0100
Jesper Dangaard Brouer <brouer@...hat.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@...hat.com>

Acked-by: Steven Rostedt <rostedt@...dmis.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.
>