linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH 3/4] trace-filter: Change the naming convention used in trace-filter-hash
Date: Mon, 18 Jun 2018 11:24:27 -0400	[thread overview]
Message-ID: <20180618112427.4a5c318e@gandalf.local.home> (raw)
In-Reply-To: <20180615212131.28121-4-y.karadz@gmail.com>


Hi Yordan,

I pulled in the first two patches.

On Sat, 16 Jun 2018 00:21:30 +0300
"Yordan Karadzhov (VMware)" <y.karadz@gmail.com> wrote:

> trace-filter-hash implements a set of hashing tools, used when
> filtering the trace data. So far these tools are used for a task
> filtering exploiting the unique Id of the task (pid). The same
> instruments can be used by an application for event filtering,
> using the unique Id of the trace event. In this patch the naming
> convention used in trace-filter-hash is changed, in order to avoid
> confusion in the case when the tools are used for event filtering.
> 

I'm not against this patch, and it makes sense. The change log could
use a little improvement though. I had to read it twice to figure out
what you were trying to do. What about something like this:

===
The trace-filter-hash code implements a set of hashing utilities for
filtering the trace data. Currently, only tasks are filtered with this
utility via its pid. To use this tool for filtering other items such as
events, a name change is required for the structures and functions
used. Instead of using the term "task", use the term "id", which is
more generic, and will be less confusing when using the
trace-filter-hash for filtering events and such.
===

Or something similar to the above. Again, the patch is fine, just the
change log was hard to understand.

-- Steve


> Signed-off-by: Yordan Karadzhov (VMware) <y.karadz@gmail.com>
> ---
>

  reply	other threads:[~2018-06-18 15:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-15 21:21 [PATCH 0/4]trace-filter: Detach trace-filter-hash from KS GUI Yordan Karadzhov (VMware)
2018-06-15 21:21 ` [PATCH 1/4] trace-cmd: Header files management in trace-hash.h Yordan Karadzhov (VMware)
2018-06-15 21:21 ` [PATCH 2/4] trace-filter: Remove the Gtk dependency in trace-filter-hash Yordan Karadzhov (VMware)
2018-06-15 21:21 ` [PATCH 3/4] trace-filter: Change the naming convention used " Yordan Karadzhov (VMware)
2018-06-18 15:24   ` Steven Rostedt [this message]
2018-06-19 13:13     ` Yordan Karadzhov (VMware)
2018-06-15 21:21 ` [PATCH 4/4] trace-filter: Change the hashing function used when filtering Yordan Karadzhov (VMware)
2018-06-18 15:28   ` 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=20180618112427.4a5c318e@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=y.karadz@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;
as well as URLs for NNTP newsgroup(s).