From: Steven Rostedt <rostedt@goodmis.org>
To: Ceco <tz.stoyanov@gmail.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH v2] Introduce new libtracevent API: tep_override_comm()
Date: Tue, 16 Oct 2018 07:43:34 -0400 [thread overview]
Message-ID: <20181016074334.25a13802@gandalf.local.home> (raw)
In-Reply-To: <CAPpZLN6bvSTVq6NBXHPKqH4cMXTxSKeTxk0VMiTAZJpt4mY_5Q@mail.gmail.com>
On Tue, 16 Oct 2018 09:46:07 +0300
Ceco <tz.stoyanov@gmail.com> wrote:
> ping
> Hi Steven, is there a problem with this patch ? Yordan needs these
> changes, he wants to use the new API in KernelShark.
Just woke up, so I haven't had a chance to look at the patch. But the
one thing that is wrong with it, is that a v2 shouldn't be a reply to a
v1. That is, it should start a new thread. With thousands of emails in
my Inbox, I look at email threads (as do many kernel developers), and
if there's a patch within the thread, it is commonly missed.
I will say that I did mark it to look at it, so I did see it. But other
patches came in during that time, and I sorted my inbox by thread, which
did hide the patch again.
I'll take a look at it later today.
Also, don't be afraid to send a ping if there's no response for a week,
as that usually means it was lost in the flood.
Thanks!
-- Steve
>
> On Fri, Aug 31, 2018 at 9:27 AM Tzvetomir Stoyanov (VMware)
> <tz.stoyanov@gmail.com> wrote:
> >
next prev parent reply other threads:[~2018-10-16 19:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 15:09 [PATCH] Introduce new libtracevent API: tep_override_comm() Tzvetomir Stoyanov (VMware)
2018-08-30 16:32 ` Steven Rostedt
2018-08-31 6:27 ` [PATCH v2] " Tzvetomir Stoyanov (VMware)
2018-10-16 6:46 ` Ceco
2018-10-16 11:43 ` Steven Rostedt [this message]
2018-10-16 18:22 ` Steven Rostedt
-- strict thread matches above, loose matches on Subject: below --
2018-10-17 7:43 Tzvetomir Stoyanov
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=20181016074334.25a13802@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=tz.stoyanov@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).