From: Hou Pu <houpu.main@gmail.com>
To: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>,
"sagi@grimberg.me" <sagi@grimberg.me>, "hch@lst.de" <hch@lst.de>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH 1/2] nvmet: return proper error code from discovery ctrl
Date: Wed, 31 Mar 2021 10:16:18 +0800 [thread overview]
Message-ID: <5269963f-8e78-866c-2dd6-ecd5887fbc13@gmail.com> (raw)
In-Reply-To: <BYAPR04MB49659B3B3301DA5EADDD49EF867D9@BYAPR04MB4965.namprd04.prod.outlook.com>
On 2021/3/31 7:29 AM, Chaitanya Kulkarni wrote:
> On 3/30/21 04:59, Hou Pu wrote:
>> Return NVME_SC_INVALID_FIELD from discovery controller
>> like normal controller when executing identify or
>> get log page command.
>>
>> Signed-off-by: Hou Pu <houpu.main@gmail.com>
> Commit could be :-
>
> Return NVME_SC_INVALID_FIELD from discovery controller like normal
> controller when executing identify or get log page command.
>
> Can be done at the time of applying the patch.
>
> With that looks good.
>
> Reviewed-by: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
>
Thanks,
Hou
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-03-31 2:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 11:59 [PATCH 0/2] Improve response status code of nvme target Hou Pu
2021-03-30 11:59 ` [PATCH 1/2] nvmet: return proper error code from discovery ctrl Hou Pu
2021-03-30 23:29 ` Chaitanya Kulkarni
2021-03-31 2:16 ` Hou Pu [this message]
2021-03-30 11:59 ` [PATCH 2/2] nvmet: remove unneeded code from nvmet_alloc_ctrl() Hou Pu
2021-03-30 23:30 ` Chaitanya Kulkarni
2021-03-31 2:18 ` Hou Pu
2021-03-31 6:22 ` Chaitanya Kulkarni
2021-03-31 6:36 ` Hou Pu
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=5269963f-8e78-866c-2dd6-ecd5887fbc13@gmail.com \
--to=houpu.main@gmail.com \
--cc=Chaitanya.Kulkarni@wdc.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 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.