linux-btrace.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: linux-btrace@vger.kernel.org
Subject: Re: [PATCH] blkparse: exit with error if no tracefiles found
Date: Mon, 19 Apr 2010 17:14:56 +0000	[thread overview]
Message-ID: <20100419171456.GY27497@kernel.dk> (raw)
In-Reply-To: <4A0B46BD.4030202@redhat.com>

On Mon, Apr 19 2010, Eric Sandeen wrote:
> Eric Sandeen wrote:
> > If no tracefiles are found, exit with non-0 status
> > 
> > Resolves Red Hat Bugzilla #500118
> > 
> > Reported-by: Milos Malik <mmalik@redhat.com>
> > Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> > ---
> 
> Re-ping on this?

Wow, that's old. Applied, sorry about that :-)

-- 
Jens Axboe


  parent reply	other threads:[~2010-04-19 17:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-13 22:16 [PATCH] blkparse: exit with error if no tracefiles found Eric Sandeen
2010-04-19 17:13 ` Eric Sandeen
2010-04-19 17:14 ` Jens Axboe [this message]
2010-04-19 17:27 ` Eric Sandeen

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=20100419171456.GY27497@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=linux-btrace@vger.kernel.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).