From: Steven Rostedt <rostedt@goodmis.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Masanari Iida <standby24x7@gmail.com>,
mingo@redhat.com, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] linux-next: ftrace/docs: Fix spelling typos in ftrace-users.rst
Date: Fri, 27 Apr 2018 18:17:09 -0400 [thread overview]
Message-ID: <20180427181709.06bc0b1b@gandalf.local.home> (raw)
In-Reply-To: <20171127224636.7c0850d3@gandalf.local.home>
I just noticed that this was never applied.
Jon, can you take this?
-- Steve
On Mon, 27 Nov 2017 22:46:36 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> 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
next prev parent reply other threads:[~2018-04-27 22:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 3:26 Masanari Iida
2017-11-28 3:46 ` Steven Rostedt
2018-04-27 22:17 ` Steven Rostedt [this message]
2018-04-27 22:31 ` Jonathan Corbet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180427181709.06bc0b1b@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=standby24x7@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®