diff options
| author | Akhil Raj <lf32.dev@gmail.com> | 2022-08-29 09:52:39 +0300 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2022-09-27 22:21:43 +0300 |
| commit | 7f77ebbf758be6df89951713e7b234a9e6c5d32b (patch) | |
| tree | de067ec255b08220cc3c5dbd4d5ea0ec4bc32fb0 /Documentation/trace | |
| parent | 32a3a9db16eb7551a6763820a8ed6f151f879eaa (diff) | |
| download | linux-7f77ebbf758be6df89951713e7b234a9e6c5d32b.tar.xz | |
Delete duplicate words from kernel docs
I have deleted duplicate words like
to, guest, trace, when, we
Signed-off-by: Akhil Raj <lf32.dev@gmail.com>
Link: https://lore.kernel.org/r/20220829065239.4531-1-lf32.dev@gmail.com
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/trace')
| -rw-r--r-- | Documentation/trace/histogram.rst | 2 | ||||
| -rw-r--r-- | Documentation/trace/timerlat-tracer.rst | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/trace/histogram.rst b/Documentation/trace/histogram.rst index 859fd1b76c63..c1b685a38f6b 100644 --- a/Documentation/trace/histogram.rst +++ b/Documentation/trace/histogram.rst @@ -412,7 +412,7 @@ Extended error information Because the default sort key above is 'hitcount', the above shows a the list of call_sites by increasing hitcount, so that at the bottom we see the functions that made the most kmalloc calls during the - run. If instead we we wanted to see the top kmalloc callers in + run. If instead we wanted to see the top kmalloc callers in terms of the number of bytes requested rather than the number of calls, and we wanted the top caller to appear at the top, we can use the 'sort' parameter, along with the 'descending' modifier:: diff --git a/Documentation/trace/timerlat-tracer.rst b/Documentation/trace/timerlat-tracer.rst index d643c95c01eb..db17df312bc8 100644 --- a/Documentation/trace/timerlat-tracer.rst +++ b/Documentation/trace/timerlat-tracer.rst @@ -20,7 +20,7 @@ For example:: [root@f32 ~]# cd /sys/kernel/tracing/ [root@f32 tracing]# echo timerlat > current_tracer -It is possible to follow the trace by reading the trace trace file:: +It is possible to follow the trace by reading the trace file:: [root@f32 tracing]# cat trace # tracer: timerlat |