Skip to content

Commit aea74de

Browse files
standby24x7Jonathan Corbet
authored andcommitted
docs: Fix typos in histogram.rst
This patch fixes some spelling typos. Signed-off-by: Masanari Iida <standby24x7@gmail.com> Acked-by: Randy Dunlap <rdunlap@infradead.org> Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
1 parent 84253c8 commit aea74de

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

Documentation/trace/histogram.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1765,7 +1765,7 @@ For example, here's how a latency can be calculated::
17651765
# echo 'hist:keys=pid,prio:ts0=common_timestamp ...' >> event1/trigger
17661766
# echo 'hist:keys=next_pid:wakeup_lat=common_timestamp-$ts0 ...' >> event2/trigger
17671767

1768-
In the first line above, the event's timetamp is saved into the
1768+
In the first line above, the event's timestamp is saved into the
17691769
variable ts0. In the next line, ts0 is subtracted from the second
17701770
event's timestamp to produce the latency, which is then assigned into
17711771
yet another variable, 'wakeup_lat'. The hist trigger below in turn
@@ -1811,7 +1811,7 @@ the command that defined it with a '!'::
18111811
/sys/kernel/debug/tracing/synthetic_events
18121812

18131813
At this point, there isn't yet an actual 'wakeup_latency' event
1814-
instantiated in the event subsytem - for this to happen, a 'hist
1814+
instantiated in the event subsystem - for this to happen, a 'hist
18151815
trigger action' needs to be instantiated and bound to actual fields
18161816
and variables defined on other events (see Section 2.2.3 below on
18171817
how that is done using hist trigger 'onmatch' action). Once that is
@@ -1837,7 +1837,7 @@ output can be displayed by reading the event's 'hist' file.
18371837
A hist trigger 'action' is a function that's executed whenever a
18381838
histogram entry is added or updated.
18391839

1840-
The default 'action' if no special function is explicity specified is
1840+
The default 'action' if no special function is explicitly specified is
18411841
as it always has been, to simply update the set of values associated
18421842
with an entry. Some applications, however, may want to perform
18431843
additional actions at that point, such as generate another event, or

0 commit comments

Comments
 (0)