From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>
Cc: Tejun Heo <tj@kernel.org>,
linux-block@vger.kernel.org, dm-devel@redhat.com,
linux-raid@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [dm-devel] block tracepoint cleanups v2
Date: Fri, 4 Dec 2020 09:42:08 -0700 [thread overview]
Message-ID: <8859c43f-a1fa-60dc-ea27-4a126f95dc68@kernel.dk> (raw)
In-Reply-To: <20201203162139.2110977-1-hch@lst.de>
On 12/3/20 9:21 AM, Christoph Hellwig wrote:
> Hi Jens,
>
> this series cleans up the block layer tracepoints by removing unused
> tracepoints or tracepoint arguments and consolidating the implementation
> of various bio based tracepoints.
Applied, thanks.
--
Jens Axboe
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
prev parent reply other threads:[~2020-12-04 16:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 16:21 [dm-devel] block tracepoint cleanups v2 Christoph Hellwig
2020-12-03 16:21 ` [dm-devel] [PATCH 1/5] block: remove the unused block_sleeprq tracepoint Christoph Hellwig
2020-12-03 19:45 ` Tejun Heo
2020-12-04 3:25 ` Chaitanya Kulkarni
2020-12-03 16:21 ` [dm-devel] [PATCH 2/5] block: simplify and extend the block_bio_merge tracepoint class Christoph Hellwig
2020-12-03 20:05 ` Tejun Heo
2020-12-04 3:25 ` Chaitanya Kulkarni
2020-12-03 16:21 ` [dm-devel] [PATCH 3/5] block: remove the request_queue argument to the block_split tracepoint Christoph Hellwig
2020-12-03 20:06 ` Tejun Heo
2020-12-04 3:26 ` Chaitanya Kulkarni
2020-12-03 16:21 ` [dm-devel] [PATCH 4/5] block: remove the request_queue argument to the block_bio_remap tracepoint Christoph Hellwig
2020-12-03 20:07 ` Tejun Heo
2020-12-04 3:27 ` Chaitanya Kulkarni
2020-12-03 16:21 ` [dm-devel] [PATCH 5/5] block: remove the request_queue to argument request based tracepoints Christoph Hellwig
2020-12-03 20:10 ` Tejun Heo
2020-12-04 3:26 ` Chaitanya Kulkarni
2020-12-04 16:42 ` 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=8859c43f-a1fa-60dc-ea27-4a126f95dc68@kernel.dk \
--to=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=tj@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).