Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1664753 > unrolled thread
| Started by | Jesper Dangaard Brouer <brouer@redhat.com> |
|---|---|
| First post | 2017-06-13 13:10 +0200 |
| Last post | 2017-06-13 13:10 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
[PATCH] trivial: tracing: spelling fixes for CONFIG_HWLAT_TRACER Jesper Dangaard Brouer <brouer@redhat.com> - 2017-06-13 13:10 +0200
| From | Jesper Dangaard Brouer <brouer@redhat.com> |
|---|---|
| Date | 2017-06-13 13:10 +0200 |
| Subject | [PATCH] trivial: tracing: spelling fixes for CONFIG_HWLAT_TRACER |
| Message-ID | <tRRRV-7ec-23@gated-at.bofh.it> |
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>
---
Resend of: https://patchwork.kernel.org/patch/9405223/
kernel/trace/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
index 7e06f04e98fe..f4215132cb91 100644
--- a/kernel/trace/Kconfig
+++ b/kernel/trace/Kconfig
@@ -224,7 +224,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
@@ -239,7 +239,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.
Back to top | Article view | linux.kernel
csiph-web