From: Joe Perches <joe@perches.com>
To: Thadeu Lima de Souza Cascardo <cascardo@canonical.com>
Cc: linux-kernel@vger.kernel.org, rostedt@goodmis.org, mingo@redhat.com
Subject: Re: [PATCH] ftrace: use non-archaic spelling of failes
Date: Thu, 31 May 2018 08:20:57 -0700 [thread overview]
Message-ID: <64b8dfb76df41105954daf0d98427a4641ba8f04.camel@perches.com> (raw)
In-Reply-To: <20180531151653.GA3903@calabresa>
On Thu, 2018-05-31 at 12:16 -0300, Thadeu Lima de Souza Cascardo wrote:
> On Thu, May 31, 2018 at 08:15:45AM -0700, Joe Perches wrote:
> > On Thu, 2018-05-31 at 09:17 -0300, Thadeu Lima de Souza Cascardo wrote:
> > > diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c
> > []
> > > @@ -4788,7 +4788,7 @@ ftrace_set_addr(struct ftrace_ops *ops, unsigned long ip, int remove,
> > > * @reset - non zero to reset all filters before applying this filter.
> > > *
> > > * Filters denote which functions should be enabled when tracing is enabled
> > > - * If @ip is NULL, it failes to update filter.
> > > + * If @ip is NULL, it fails to update filter.
> > > */
> > > int ftrace_set_filter_ip(struct ftrace_ops *ops, unsigned long ip,
> > > int remove, int reset)
> >
> > Perhaps fix it treewide?
> >
> > $ git grep -w -i failes | wc -l
> > 8
>
> I sent patches to the respective maintainers for all of these.
Great, thank you.
next prev parent reply other threads:[~2018-05-31 15:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 12:17 Thadeu Lima de Souza Cascardo
2018-05-31 15:15 ` Joe Perches
2018-05-31 15:16 ` Thadeu Lima de Souza Cascardo
2018-05-31 15:20 ` Joe Perches [this message]
2018-05-31 22:46 ` Steven Rostedt
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=64b8dfb76df41105954daf0d98427a4641ba8f04.camel@perches.com \
--to=joe@perches.com \
--cc=cascardo@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.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®