linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-trace-devel@vger.kernel.org
Cc: Yordan Karadzhov <y.karadz@gmail.com>
Subject: Re: [PATCH 0/4] kernel-shark: The road to 1.0
Date: Tue, 16 Jul 2019 20:24:44 -0400	[thread overview]
Message-ID: <20190716202444.413809fa@gandalf.local.home> (raw)
In-Reply-To: <20190710134636.116362181@goodmis.org>

On Wed, 10 Jul 2019 09:46:36 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:

> Some fixes for getting to 1.0.
> 
> Steven Rostedt (VMware) (3):
>       revert: "kernel-shark: Remove a duplicate error message"
>       kernel-shark: Show the standard error of kshark-record
>       kernel-shark: Use '<br>' for dialog and '\n' for console error messages
> 
> Yordan Karadzhov (VMware) (1):
>       kernel-shark: Remove the "make install" suggestion for capture errors
> 

Hi Yordan,

Can you review these patches?

Thanks!

-- Steve

      parent reply	other threads:[~2019-07-17  0:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-10 13:46 [PATCH 0/4] kernel-shark: The road to 1.0 Steven Rostedt
2019-07-10 13:46 ` [PATCH 1/4] revert: "kernel-shark: Remove a duplicate error message" Steven Rostedt
2019-07-10 13:46 ` [PATCH 2/4] kernel-shark: Remove the "make install" suggestion for capture errors Steven Rostedt
2019-07-10 13:46 ` [PATCH 3/4] kernel-shark: Show the standard error of kshark-record Steven Rostedt
2019-07-10 13:46 ` [PATCH 4/4] kernel-shark: Use <br> for dialog and \n for console error messages Steven Rostedt
2019-07-17  6:55   ` Yordan Karadzhov (VMware)
2019-07-17  0:24 ` Steven Rostedt [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=20190716202444.413809fa@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).