Re: [PATCH] linux-next: ftrace/docs: Fix spelling typos in ftrace-users.rst
From: Steven Rostedt
Date: Fri Apr 27 2018 - 18:17:18 EST
I just noticed that this was never applied.
Jon, can you take this?
On Mon, 27 Nov 2017 22:46:36 -0500
Steven Rostedt <rostedt@xxxxxxxxxxx> wrote:
> On Tue, 28 Nov 2017 12:26:13 +0900
> Masanari Iida <standby24x7@xxxxxxxxx> wrote:
> > This patch corrects some spelling typo in ftrace-users.rst
> > Signed-off-by: Masanari Iida <standby24x7@xxxxxxxxx>
> > ---
> > 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@xxxxxxxxxxx>
> -- Steve