From: Hou Pu <houpu.main@gmail.com>
To: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH 2/2] nvmet: remove unneeded code from nvmet_alloc_ctrl()
Date: Wed, 31 Mar 2021 14:36:08 +0800 [thread overview]
Message-ID: <6a25ad2c-8b07-50dd-e40b-246696cf0bd6@gmail.com> (raw)
In-Reply-To: <5F1FE896-F02E-401B-981B-D7D8C0E5CBC7@wdc.com>
On 2021/3/31 2:22 PM, Chaitanya Kulkarni wrote:
>
> On 3/30/21, 7:18 PM, "Hou Pu" <houpu.main@gmail.com> wrote:
>
>
> On 2021/3/31 7:30 上午, Chaitanya Kulkarni wrote:
> > On 3/30/21 04:59, Hou Pu wrote:
> >> Signed-off-by: Hou Pu <houpu.main@gmail.com>
> >> ---
> >> drivers/nvme/target/core.c | 1 -
> >> 1 file changed, 1 deletion(-)
> > On what branch you have generated this patch ?
> >
> >
> The patch is based on v5.12-rc4.
>
> (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/nvme/target/core.c?h=v5.12-rc4#n1328)
>
>
> Thanks,
>
> Hou
>
>
> I think I've fixed this in 5.13, please check, if so we may need to drop this patch.
Yes, just notice that from nvme.git tree. Thanks.
I will drop this in v2.
Thanks,
Hou
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2021-03-31 6:36 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
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 [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=6a25ad2c-8b07-50dd-e40b-246696cf0bd6@gmail.com \
--to=houpu.main@gmail.com \
--cc=Chaitanya.Kulkarni@wdc.com \
--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