lkml.org 
[lkml]   [2017]   [Nov]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] linux-next: ftrace/docs: Fix spelling typos in ftrace-users.rst
On Tue, 28 Nov 2017 12:26:13 +0900
Masanari Iida <standby24x7@gmail.com> wrote:

> This patch corrects some spelling typo in ftrace-users.rst
>
> Signed-off-by: Masanari Iida <standby24x7@gmail.com>
> ---
> Documentation/trace/ftrace-uses.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/trace/ftrace-uses.rst b/Documentation/trace/ftrace-uses.rst
> index 8494a801d341..9df5ee15859a 100644
> --- a/Documentation/trace/ftrace-uses.rst
> +++ b/Documentation/trace/ftrace-uses.rst
> @@ -12,7 +12,7 @@ Written for: 4.14
> Introduction
> ============
>
> -The ftrace infrastructure was originially created to attach callbacks to the
> +The ftrace infrastructure was originally created to attach callbacks to the
> beginning of functions in order to record and trace the flow of the kernel.
> But callbacks to the start of a function can have other use cases. Either
> for live kernel patching, or for security monitoring. This document describes
> @@ -29,7 +29,7 @@ going to idle, during CPU bring up and takedown, or going to user space.
> This requires extra care to what can be done inside a callback. A callback
> can be called outside the protective scope of RCU.
>
> -The ftrace infrastructure has some protections agains recursions and RCU
> +The ftrace infrastructure has some protections against recursions and RCU
> but one must still be very careful how they use the callbacks.
>
>

Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>

-- Steve

\
 
 \ /
  Last update: 2017-11-28 04:47    [W:0.070 / U:0.168 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site