History

tracing/trivial: Fix typos and make an int into a bool

Fix up a few typos in comments and convert an int into a bool in update_traceon_count(). Link: http://lkml.kernel.org/r/546DD445.5080108@hitachi.com

Steven Rostedt (Red Hat) committed 11 years ago

Commit 0af26491 parent 16a8ef22 files · +4 −4Browse files

Showing the changes to kernel/trace (2 of 2 files). Show all

Unified · Split

2 files
  1. kernel/trace/ftrace.c +1 −1
  2. kernel/trace/trace_functions.c +3 −3
kernel/trace/ftrace.c+1−1
@@ -1119,7 +1119,7 @@ static struct ftrace_ops global_ops = { · 1118 unmodified lines
11191119
11201120 /*
11211121 * This is used by __kernel_text_address() to return true if the
1122− * the address is on a dynamically allocated trampoline that would
1122+ * address is on a dynamically allocated trampoline that would
11231123 * not return true for either core_kernel_text() or
11241124 * is_module_text_address().
11251125 */
kernel/trace/trace_functions.c+3−3
@@ -261,14 +261,14 @@ static struct tracer function_trace __tracer_data = · 260 unmodified lines
261261 };
262262
263263 #ifdef CONFIG_DYNAMIC_FTRACE
264−static void update_traceon_count(void **data, int on)
264+static void update_traceon_count(void **data, bool on)
265265 {
266266 long *count = (long *)data;
267267 long old_count = *count;
268268
269269 /*
270270 * Tracing gets disabled (or enabled) once per count.
271− * This function can be called at the same time on mulitple CPUs.
271+ * This function can be called at the same time on multiple CPUs.
272272 * It is fine if both disable (or enable) tracing, as disabling
273273 * (or enabling) the second time doesn't do anything as the
274274 * state of the tracer is already disabled (or enabled).
@@ -288,7 +288,7 @@ static void update_traceon_count(void **data, int on) · 13 unmodified lines
288288 * the new state is visible before changing the counter by
289289 * one minus the old counter. This guarantees that another CPU
290290 * executing this code will see the new state before seeing
291− * the new counter value, and would not do anthing if the new
291+ * the new counter value, and would not do anything if the new
292292 * counter is seen.
293293 *
294294 * Note, there is no synchronization between this and a user