From: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
To: "Engel, Amit" <Amit.Engel@Dell.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"james.smart@broadcom.com" <james.smart@broadcom.com>
Cc: James Smart <jsmart2021@gmail.com>
Subject: Re: [PATCH] nvmet-fc: simplify nvmet_fc_alloc_hostport
Date: Fri, 26 Mar 2021 19:02:44 +0000 [thread overview]
Message-ID: <BYAPR04MB49651D211A8D26C40EB52C0386619@BYAPR04MB4965.namprd04.prod.outlook.com> (raw)
In-Reply-To: BL0PR1901MB2020C91B6489355411A00578EE619@BL0PR1901MB2020.namprd19.prod.outlook.com
On 3/26/21 06:32, Engel, Amit wrote:
> Hi, are we OK with this patch? please let me know if there is anything that is missing/required
>
> Thanks
> Amit E
Looks good.
Reviewed-by: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
_______________________________________________
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-26 19:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 19:57 [PATCH] nvmet-fc: simplify nvmet_fc_alloc_hostport amit.engel
2021-03-26 13:32 ` Engel, Amit
2021-03-26 19:02 ` Chaitanya Kulkarni [this message]
2021-04-04 11:41 ` Engel, Amit
2021-04-10 6:45 ` Christoph Hellwig
2021-04-10 14:27 ` James Smart
2021-04-12 7:48 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2021-03-22 18:59 amit.engel
2021-03-22 19:11 ` Chaitanya Kulkarni
2021-03-22 19:13 ` Chaitanya Kulkarni
2021-03-22 19:15 ` Chaitanya Kulkarni
2021-03-22 19:37 ` James Smart
2021-03-22 19:40 ` Chaitanya Kulkarni
2021-03-16 6:43 amit.engel
2021-03-17 21:28 ` Himanshu Madhani
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=BYAPR04MB49651D211A8D26C40EB52C0386619@BYAPR04MB4965.namprd04.prod.outlook.com \
--to=chaitanya.kulkarni@wdc.com \
--cc=Amit.Engel@Dell.com \
--cc=james.smart@broadcom.com \
--cc=jsmart2021@gmail.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;
as well as URLs for NNTP newsgroup(s).