From: Johannes Thumshirn <johannes.thumshirn@wdc.com>
To: "axboe@kernel.dk" <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Damien Le Moal <dlemoal@kernel.org>,
Christoph Hellwig <hch@lst.de>,
Chaitanya Kulkarni <chaitanyak@nvidia.com>,
linux-btrace@vger.kernel.org
Subject: Re: [PATCH v2 00/11] blktrace: parse blk_io_trace2 in btt and iowatcher
Date: Fri, 2 Oct 2026 09:53:34 +0200 [thread overview]
Message-ID: <ar9i3yI8WALfVpGj@mayhem.fritz.box> (raw)
In-Reply-To: <arPISNMA9LiFR8_w@mayhem.fritz.box>
On Wed, Sep 23, 2026 at 02:38:59PM +0200, Johannes Thumshirn wrote:
> On Mon, Jul 20, 2026 at 01:14:06PM +0200, Johannes Thumshirn wrote:
> > We had an internal report that the new blktrace format does not work
> > with the btt tool.
> >
> > This is because I simply forgot to update these tools. Do so now and
> > sorry for all the inconvenience it might have brought.
>
> Jens, ping?
>
Jens, is there anything else I need do to get this series merged?
next prev parent reply other threads:[~2026-10-02 7:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 11:14 [PATCH v2 00/11] blktrace: parse blk_io_trace2 in btt and iowatcher Johannes Thumshirn
2026-07-20 11:14 ` [PATCH v2 01/11] btt: use blk_io_trace2 internally Johannes Thumshirn
2026-07-20 11:14 ` [PATCH v2 02/11] btt: natively parse blk_io_trace2 Johannes Thumshirn
2026-07-20 11:14 ` [PATCH v2 03/11] blktrace: add option to request a specific trace protocol version Johannes Thumshirn
2026-07-20 11:52 ` Damien Le Moal
2026-07-20 11:14 ` [PATCH v2 04/11] blkrawverify: use blk_io_trace2 internally Johannes Thumshirn
2026-07-20 11:14 ` [PATCH v2 05/11] blkrawverify: natively parse blk_io_trace2 Johannes Thumshirn
2026-07-20 11:14 ` [PATCH v2 06/11] blkiomon: use blk_io_trace2 internally Johannes Thumshirn
2026-07-20 11:14 ` [PATCH v2 07/11] blkiomon: natively parse blk_io_trace2 Johannes Thumshirn
2026-07-20 11:14 ` [PATCH v2 08/11] iowatcher: use blk_io_trace2 internally Johannes Thumshirn
2026-07-20 11:14 ` [PATCH v2 09/11] iowatcher: natively parse blk_io_trace2 Johannes Thumshirn
2026-07-20 11:14 ` [PATCH v2 10/11] btreplay: support blk_io_trace2 in btrecord Johannes Thumshirn
2026-07-20 11:14 ` [PATCH v2 11/11] blkparse: add option to emit a specific trace protocol version Johannes Thumshirn
2026-09-23 12:38 ` [PATCH v2 00/11] blktrace: parse blk_io_trace2 in btt and iowatcher Johannes Thumshirn
2026-10-02 7:53 ` Johannes Thumshirn [this message]
2026-10-02 14:25 ` Jens Axboe
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=ar9i3yI8WALfVpGj@mayhem.fritz.box \
--to=johannes.thumshirn@wdc.com \
--cc=axboe@kernel.dk \
--cc=chaitanyak@nvidia.com \
--cc=dlemoal@kernel.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--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