From: Christoph Hellwig <hch@lst.de>
To: Guixin Liu <kanie@linux.alibaba.com>
Cc: hch@lst.de, sagi@grimberg.me, kch@nvidia.com,
d.bogdanov@yadro.com, linux-nvme@lists.infradead.org
Subject: Re: [PATCH v13 1/2] nvme: add reservation command's defines
Date: Thu, 10 Oct 2024 11:27:28 +0200 [thread overview]
Message-ID: <20241010092728.GA9749@lst.de> (raw)
In-Reply-To: <20241008102114.26199-2-kanie@linux.alibaba.com>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2024-10-10 9:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 10:21 [PATCH v13 0/2] Implement the NVMe reservation feature Guixin Liu
2024-10-08 10:21 ` [PATCH v13 1/2] nvme: add reservation command's defines Guixin Liu
2024-10-10 9:27 ` Christoph Hellwig [this message]
2024-10-08 10:21 ` [PATCH v13 2/2] nvmet: support reservation feature Guixin Liu
2024-10-08 10:37 ` Dmitry Bogdanov
2024-10-10 9:30 ` Christoph Hellwig
2024-10-11 2:22 ` Guixin Liu
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=20241010092728.GA9749@lst.de \
--to=hch@lst.de \
--cc=d.bogdanov@yadro.com \
--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;
as well as URLs for NNTP newsgroup(s).