From: Christoph Hellwig <hch@lst.de>
To: Guixin Liu <kanie@linux.alibaba.com>
Cc: kbusch@kernel.org, axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
kch@nvidia.com, linux-nvme@lists.infradead.org
Subject: Re: [PATCH 2/2] nvmet: add tracing of reservation commands
Date: Tue, 15 Oct 2024 06:54:48 +0200 [thread overview]
Message-ID: <20241015045448.GC18058@lst.de> (raw)
In-Reply-To: <20241014101458.80491-3-kanie@linux.alibaba.com>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2024-10-15 4:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 10:14 [PATCH 0/2] Add the tracing of reservation commands Guixin Liu
2024-10-14 10:14 ` [PATCH 1/2] nvme: parse reservation commands's action and rtype to string Guixin Liu
2024-10-14 18:26 ` Chaitanya Kulkarni
2024-10-15 4:54 ` Christoph Hellwig
2024-10-20 23:50 ` Sagi Grimberg
2024-10-14 10:14 ` [PATCH 2/2] nvmet: add tracing of reservation commands Guixin Liu
2024-10-14 18:27 ` Chaitanya Kulkarni
2024-10-15 4:54 ` Christoph Hellwig [this message]
2024-10-20 23:50 ` Sagi Grimberg
2024-11-13 10:44 ` [PATCH 0/2] Add the " Guixin Liu
2024-11-13 16:58 ` Keith Busch
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=20241015045448.GC18058@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=kanie@linux.alibaba.com \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.