Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Guixin Liu <kanie@linux.alibaba.com>
To: Chaitanya Kulkarni <chaitanyak@nvidia.com>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	"sagi@grimberg.me" <sagi@grimberg.me>, "hch@lst.de" <hch@lst.de>
Subject: Re: [PATCH v14 1/2] nvme: add reservation command's defines
Date: Mon, 14 Oct 2024 14:00:30 +0800	[thread overview]
Message-ID: <2b10b220-7069-400a-8b82-a20a69a58478@linux.alibaba.com> (raw)
In-Reply-To: <519ebe04-a2b1-4e9a-a67f-7bfb810a7d88@nvidia.com>


在 2024/10/14 13:43, Chaitanya Kulkarni 写道:
> On 10/10/24 19:26, Guixin Liu wrote:
>> This is a prepath of reservation implementation patch.
> if it makes sense please consider something like :-
>
> This is a preparation patch for NVMeOF target reservation
> commands implantation.
OK, I will send the v15 to change it.
>> Add the defines of reservation command, such as reservation log
>> and sub operations.
>>
>> Signed-off-by: Guixin Liu <kanie@linux.alibaba.com>
>> ---
>>
> Looks good.
>
> Tested-by: Chaitanya Kulkarni <kch@nvidia.com>
> Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
>
> -ck
>
>


  reply	other threads:[~2024-10-14  6:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-11  2:26 [PATCH v14 0/2] Implement the NVMe reservation feature Guixin Liu
2024-10-11  2:26 ` [PATCH v14 1/2] nvme: add reservation command's defines Guixin Liu
2024-10-14  5:43   ` Chaitanya Kulkarni
2024-10-14  6:00     ` Guixin Liu [this message]
2024-10-11  2:26 ` [PATCH v14 2/2] nvmet: support reservation feature Guixin Liu
2024-10-11  7:48   ` Dmitry Bogdanov
2024-10-11  8:10   ` Christoph Hellwig
2024-10-14  4:04   ` Chaitanya Kulkarni
2024-10-14  5:34     ` Guixin Liu
2024-10-14  6:18       ` Chaitanya Kulkarni
2024-10-14  6:31         ` Guixin Liu
2024-10-15  5:00       ` hch
2024-10-14  6:05   ` Chaitanya Kulkarni

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=2b10b220-7069-400a-8b82-a20a69a58478@linux.alibaba.com \
    --to=kanie@linux.alibaba.com \
    --cc=chaitanyak@nvidia.com \
    --cc=hch@lst.de \
    --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