From: Randy Dunlap <rdunlap@infradead.org>
To: "Frank A. Cancio Bello" <frank@generalsoftwareinc.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: joel@joelfernandes.org, saiprakash.ranjan@codeaurora.org,
nachukannan@gmail.com
Subject: Re: [PATCH 2/3] docs: ftrace: Fix typos
Date: Tue, 24 Dec 2019 15:11:34 -0800 [thread overview]
Message-ID: <4d8a764c-88fe-56c0-e655-ed4052ab6d2d@infradead.org> (raw)
In-Reply-To: <638f1c8b6f4a47e4e25b62a01fe960e70a8364bc.1577209218.git.frank@generalsoftwareinc.com>
On 12/24/19 9:57 AM, Frank A. Cancio Bello wrote:
> Fix minor typos in the doc.
>
> Signed-off-by: Frank A. Cancio Bello <frank@generalsoftwareinc.com>
> ---
> Documentation/trace/ftrace.rst | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/trace/ftrace.rst b/Documentation/trace/ftrace.rst
> index 5a037bedbf6a..6c9f40d5a2f9 100644
> --- a/Documentation/trace/ftrace.rst
> +++ b/Documentation/trace/ftrace.rst
> @@ -236,7 +236,7 @@ of ftrace. Here is a list of some of the key files:
> This interface also allows for commands to be used. See the
> "Filter commands" section for more details.
>
> - As a speed up, since processing strings can't be quite expensive
> + As a speed up, since processing strings can be quite expensive
> and requires a check of all functions registered to tracing, instead
> an index can be written into this file. A number (starting with "1")
> written will instead select the same corresponding at the line position
> @@ -383,7 +383,7 @@ of ftrace. Here is a list of some of the key files:
>
> By default, 128 comms are saved (see "saved_cmdlines" above). To
> increase or decrease the amount of comms that are cached, echo
> - in a the number of comms to cache, into this file.
> + in the number of comms to cache, into this file.
That repeats the inwardness of the echo (in + into). How about:
+ the number of comms to cache into this file.
>
> saved_tgids:
>
> @@ -3325,7 +3325,7 @@ directories after it is created.
>
> As you can see, the new directory looks similar to the tracing directory
> itself. In fact, it is very similar, except that the buffer and
> -events are agnostic from the main director, or from any other
> +events are agnostic from the main directory, or from any other
> instances that are created.
>
> The files in the new directory work just like the files with the
>
--
~Randy
next prev parent reply other threads:[~2019-12-24 23:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-24 17:55 [PATCH 0/3] docs: ftrace: Fix minor issues in the doc Frank A. Cancio Bello
2019-12-24 17:56 ` [PATCH 1/3] docs: ftrace: Clarify the RAM impact of buffer_size_kb Frank A. Cancio Bello
2019-12-24 17:57 ` [PATCH 2/3] docs: ftrace: Fix typos Frank A. Cancio Bello
2019-12-24 23:11 ` Randy Dunlap [this message]
2019-12-25 0:18 ` Frank A. Cancio Bello
2019-12-24 17:58 ` [PATCH 3/3] docs: ftrace: Fix small notation mistake Frank A. Cancio Bello
2019-12-24 23:50 [PATCH 0/3] docs: ftrace: Fix minor issues in the doc Frank A. Cancio Bello
2019-12-24 23:52 ` [PATCH 2/3] docs: ftrace: Fix typos Frank A. Cancio Bello
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=4d8a764c-88fe-56c0-e655-ed4052ab6d2d@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=frank@generalsoftwareinc.com \
--cc=joel@joelfernandes.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nachukannan@gmail.com \
--cc=rostedt@goodmis.org \
--cc=saiprakash.ranjan@codeaurora.org \
/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®