From: Borislav Petkov <bp@alien8.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ftrace: Kill ftrace_caller_end label
Date: Mon, 14 Dec 2015 17:41:57 +0100 [thread overview]
Message-ID: <20151214164157.GD10520@pd.tnic> (raw)
In-Reply-To: <20151214113027.03d3587c@gandalf.local.home>
On Mon, Dec 14, 2015 at 11:30:27AM -0500, Steven Rostedt wrote:
> On Mon, 14 Dec 2015 17:08:34 +0100
> Borislav Petkov <bp@alien8.de> wrote:
>
> > From: Borislav Petkov <bp@suse.de>
> >
> > One of ftrace_caller_and and ftrace_return is redundant so unify them.
>
> s/_and/_end/
Whoops.
> > Rename ftrace_return to ftrace_epilogue to mean that everything after
> > that label represents, like an afterword, work which happens *after* the
> > ftrace call, e.g., the function graph tracer for one.
> >
> > Beef up the comment about the code contents and layout before
> > ftrace_epilogue label.
>
> According to http://www.thefreedictionary.com/epilog
>
> ep·i·logue also ep·i·log (ĕp′ə-lôg′, -lŏg′) (n).
> 1.
> a. A short poem or speech spoken directly to the audience following
> the conclusion of a play.
>
> Hmm, that doesn't fit.
Huh, why doesn't that fit?
"A short code executed following the conclusion of a trampoline..." :-)
> b. The performer who delivers such a short poem or speech.
>
> Maybe people can think ftrace as a poem. But people will never think
> that I give such a short speech.
LOL.
> 2. A short addition or concluding section at the end of a literary
> work, often dealing with the future of its characters. Also called
> afterword.
>
> Ah, "afterword" also doesn't fit, unless you mean "characters" as a set
> of "char []". Which I guess the trampoline would fit.
>
> 3. An event which reflects meaningfully on a recently ended conflict or
> struggle.
>
> Ah! This looks like the best match! Thus, this should be stated in the
> changelog!
It is simply supposed to denote "stuff done after". You can call it
ftrace_post_work, ftrace_after, ...
I'm sure you're going to fix it up as you like it when applying :-)
Thanks!
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
prev parent reply other threads:[~2015-12-14 16:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 16:08 [PATCH] ftrace: Kill ftrace_caller_end label Borislav Petkov
2015-12-14 16:30 ` Steven Rostedt
2015-12-14 16:41 ` Borislav Petkov [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=20151214164157.GD10520@pd.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--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