From: "Vladislav K. Valtchev" <vladislav.valtchev@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-trace-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
y.karadz@gmail.com
Subject: Re: [PATCH v4 1/3] trace-cmd: Make read_proc() to return int status via OUT arg
Date: Mon, 22 Jan 2018 11:03:00 +0200 [thread overview]
Message-ID: <1516611780.6836.0.camel@gmail.com> (raw)
In-Reply-To: <20180119170232.4da3f768@gandalf.local.home>
On Fri, 2018-01-19 at 17:02 -0500, Steven Rostedt wrote:
> On Fri, 19 Jan 2018 16:58:02 -0500
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > Just to let you know. I accepted all three of your patches. I have one
> > comment, (and changed this myself).
>
> Anyway,
>
> Great job so far! I think I'm all set to start getting trace-cmd 2.7
> out now. Unfortunately, I don't think I'll be able to get to that
> before I leave on my next trip.
>
> -- Steve
Thanks Steven, I'm happy that you accepted my patches!
Sure, the next time I'll use 76 (or maybe even 74) as col limit
for the description.
--
Vladislav Valtchev
VMware Open Source Technology Center
next prev parent reply other threads:[~2018-01-22 9:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 19:53 [PATCH v4 0/3] Integrate stack tracer status in 'stat' Vladislav Valtchev (VMware)
2018-01-16 19:53 ` [PATCH v4 1/3] trace-cmd: Make read_proc() to return int status via OUT arg Vladislav Valtchev (VMware)
2018-01-19 21:58 ` Steven Rostedt
2018-01-19 22:02 ` Steven Rostedt
2018-01-22 9:03 ` Vladislav K. Valtchev [this message]
2018-01-16 19:53 ` [PATCH v4 2/3] trace-cmd: Remove the die() call from read_proc() Vladislav Valtchev (VMware)
2018-01-16 19:53 ` [PATCH v4 3/3] trace-cmd: Making stat to report when the stack tracer is ON Vladislav Valtchev (VMware)
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=1516611780.6836.0.camel@gmail.com \
--to=vladislav.valtchev@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.