From: Namhyung Kim <namhyung@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH 1/3] ftrace: Factor out __ftrace_hash_move()
Date: Sat, 21 Jan 2017 09:24:59 +0900 [thread overview]
Message-ID: <20170121002459.GA23554@danjae.aot.lge.com> (raw)
In-Reply-To: <20170120122535.47c9c04f@gandalf.local.home>
Hi Steve,
On Fri, Jan 20, 2017 at 12:25:35PM -0500, Steven Rostedt wrote:
> On Fri, 20 Jan 2017 11:44:45 +0900
> Namhyung Kim <namhyung@kernel.org> wrote:
>
> > The __ftrace_hash_move() is to allocates properly-sized hash and move
> > entries in the src ftrace_hash. It will be used to set function graph
> > filters which has nothing to do with the dyn_ftrace records.
> >
> > Signed-off-by: Namhyung Kim <namhyung@kernel.org>
>
> Hmm, no cover letter?
Oh, I thought it's a conceptually simple and small patch series. So I
didn't add a cover letter. Do you prefer seeing a cover letter anyway?
>
> Anyway, I applied the patches and I'm testing them now. I took a look
> over them and they seem good, although, there's a few optimizations I
> want to add. But I'll do that later.
Thanks, if you have anything for me to do, please let me know.
Namhyung
prev parent reply other threads:[~2017-01-21 0:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 2:44 [PATCH 1/3] ftrace: Factor out __ftrace_hash_move() Namhyung Kim
2017-01-20 2:44 ` [PATCH 2/3] ftrace: Expose ftrace_hash_empty and ftrace_lookup_ip Namhyung Kim
2017-01-20 19:54 ` Steven Rostedt
2017-01-21 0:27 ` Namhyung Kim
2017-01-21 2:13 ` Steven Rostedt
2017-01-21 2:26 ` Namhyung Kim
2017-01-20 2:44 ` [PATCH 3/3] ftrace: Convert graph filter to use hash tables Namhyung Kim
2017-01-20 17:25 ` [PATCH 1/3] ftrace: Factor out __ftrace_hash_move() Steven Rostedt
2017-01-21 0:24 ` Namhyung Kim [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=20170121002459.GA23554@danjae.aot.lge.com \
--to=namhyung@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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;
as well as URLs for NNTP newsgroup(s).