From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1765242AbcJaKIc (ORCPT ); Mon, 31 Oct 2016 06:08:32 -0400 Received: from mx1.redhat.com ([209.132.183.28]:42898 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1764590AbcJaKIb (ORCPT ); Mon, 31 Oct 2016 06:08:31 -0400 Subject: [PATCH] tracing: spelling fixes for CONFIG_HWLAT_TRACER From: Jesper Dangaard Brouer To: linux-kernel@vger.kernel.org, rostedt@goodmis.org Cc: Jesper Dangaard Brouer Date: Mon, 31 Oct 2016 11:08:28 +0100 Message-ID: <20161031100828.19656.33026.stgit@firesoul> User-Agent: StGit/0.17.1-dirty MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Mon, 31 Oct 2016 10:08:30 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Trivial spelling fixes for Kconfig help text of config HWLAT_TRACER. Fixes: e7c15cd8a113 ("tracing: Added hardware latency tracer") Signed-off-by: Jesper Dangaard Brouer --- 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.