From: Jens Axboe <jens.axboe@oracle.com>
To: linux-btrace@vger.kernel.org
Subject: Re: [patch 0/2] Resend of blkparse extensions for PC requests
Date: Wed, 02 Apr 2008 07:21:36 +0000 [thread overview]
Message-ID: <20080402072136.GG12774@kernel.dk> (raw)
In-Reply-To: <20080229115936.338333000@de.ibm.com>
On Mon, Mar 31 2008, Christof Schmitt wrote:
> On Fri, Feb 29, 2008 at 09:38:58PM +0100, Jens Axboe wrote:
> > On Fri, Feb 29 2008, Christof Schmitt wrote:
> > > I am resending the blkparse extensions for PC requests from last
> > > month. They add accounting for PC requests and also use PC requests
> > > while tracking the queue depth.
> > >
> > > The patches apply cleanly to the code in the git repository.
> >
> > Thanks for doing this Christof, I'll test and apply the patches when I
> > get back on monday.
>
> Any update on this?
Sorry for the lateness, they are both applied now. Thanks!
--
Jens Axboe
prev parent reply other threads:[~2008-04-02 7:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 11:59 [patch 0/2] Resend of blkparse extensions for PC requests Christof Schmitt
2008-02-29 20:38 ` Jens Axboe
2008-03-31 19:20 ` Christof Schmitt
2008-04-02 7:21 ` Jens Axboe [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=20080402072136.GG12774@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).