From: Sagi Grimberg <sagi@grimberg.me>
To: "brookxu.cn" <brookxu.cn@gmail.com>,
kbusch@kernel.org, axboe@kernel.dk, hch@lst.de
Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvme-fabrics: use reserved tag for reg read/write command
Date: Tue, 30 Apr 2024 12:44:24 +0300 [thread overview]
Message-ID: <4f95ac4c-4243-4de6-b397-adf4637d5aa4@grimberg.me> (raw)
In-Reply-To: <20240430021753.385089-1-brookxu.cn@gmail.com>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
next prev parent reply other threads:[~2024-04-30 9:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 2:17 brookxu.cn
2024-04-30 3:46 ` Chaitanya Kulkarni
2024-04-30 5:10 ` 许春光
2024-04-30 6:59 ` Chaitanya Kulkarni
2024-04-30 8:59 ` 许春光
2024-04-30 9:44 ` Sagi Grimberg [this message]
2024-04-30 17:42 ` 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=4f95ac4c-4243-4de6-b397-adf4637d5aa4@grimberg.me \
--to=sagi@grimberg.me \
--cc=axboe@kernel.dk \
--cc=brookxu.cn@gmail.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.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
all inboxes | Powered by JetHome®