From: Steven Rostedt <rostedt@goodmis.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Haocheng Xie <xiehaocheng.cn@gmail.com>,
mingo@redhat.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: Fix typos in Documentation/trace/ftrace.rst
Date: Tue, 1 Jun 2021 22:25:27 -0400 [thread overview]
Message-ID: <20210601222527.7cea98c6@rorschach.local.home> (raw)
In-Reply-To: <87a6o98adq.fsf@meer.lwn.net>
On Tue, 01 Jun 2021 16:53:37 -0600
Jonathan Corbet <corbet@lwn.net> wrote:
> Haocheng Xie <xiehaocheng.cn@gmail.com> writes:
>
> > Fix the usage of "a/the" and improve the readability.
> >
> > Signed-off-by: Haocheng Xie <xiehaocheng.cn@gmail.com>
> > ---
> > Documentation/trace/ftrace.rst | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/Documentation/trace/ftrace.rst b/Documentation/trace/ftrace.rst
> > index 62c98e9..11cc1c2 100644
> > --- a/Documentation/trace/ftrace.rst
> > +++ b/Documentation/trace/ftrace.rst
> > @@ -354,8 +354,8 @@ of ftrace. Here is a list of some of the key files:
> > is being directly called by the function. If the count is greater
> > than 1 it most likely will be ftrace_ops_list_func().
> >
> > - If the callback of the function jumps to a trampoline that is
> > - specific to a the callback and not the standard trampoline,
> > + If the callback of a function jumps to a trampoline which is
> > + specific to the callback and which is not the standard trampoline,
>
> The "that" in the first line was actually correct and best left
> unchanged. I've applied the patch, but took the liberty of putting
> "that" back.
Right. And if it is modifying the "the" here, it should be modifying
the "the function" in the previous paragraph as well.
-- Steve
prev parent reply other threads:[~2021-06-02 2:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 8:39 [PATCH] docs: Fix typos in Documentation/trace/ftrace.rst Haocheng Xie
2021-06-01 22:53 ` Jonathan Corbet
2021-06-02 2:25 ` Steven Rostedt [this message]
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=20210601222527.7cea98c6@rorschach.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=xiehaocheng.cn@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