From: Keith Busch <kbusch@kernel.org>
To: Guixin Liu <kanie@linux.alibaba.com>
Cc: hch@lst.de, sagi@grimberg.me, kch@nvidia.com,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH v3 0/2] nvmet: add some commands tracing
Date: Fri, 8 Mar 2024 09:21:13 -0700 [thread overview]
Message-ID: <Zes6-Z9GYWWp4ivT@kbusch-mbp> (raw)
In-Reply-To: <20240228083755.125259-1-kanie@linux.alibaba.com>
Thanks, applied to nvme-6.9.
prev parent reply other threads:[~2024-03-08 16:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 8:37 [PATCH v3 0/2] nvmet: add some commands tracing Guixin Liu
2024-02-28 8:37 ` [PATCH v3 1/2] nvmet: add tracing of authentication commands Guixin Liu
2024-03-07 9:36 ` Sagi Grimberg
2024-03-08 5:44 ` Chaitanya Kulkarni
2024-02-28 8:37 ` [PATCH v3 2/2] nvmet: add tracing of zns commands Guixin Liu
2024-02-28 9:03 ` Chaitanya Kulkarni
2024-03-07 9:36 ` Sagi Grimberg
2024-03-08 16:21 ` Keith Busch [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=Zes6-Z9GYWWp4ivT@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=hch@lst.de \
--cc=kanie@linux.alibaba.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox