linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Engel, Amit" <Amit.Engel@Dell.com>
To: Daniel Wagner <dwagner@suse.de>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	Nilay Shroff <nilay@linux.ibm.com>
Cc: "kbusch@kernel.org" <kbusch@kernel.org>,
	"gjoyce@ibm.com" <gjoyce@ibm.com>
Subject: RE: [PATCH] fabrics : allow host to create duplicate connections to target
Date: Wed, 3 Apr 2024 16:43:11 +0000	[thread overview]
Message-ID: <CO1PR19MB4885EF4B56B817B4B1C3FB24EE3D2@CO1PR19MB4885.namprd19.prod.outlook.com> (raw)
In-Reply-To: <171215230057.21309.17076148857202676100.b4-ty@suse.de>

Looks good, thank you!


Internal Use - Confidential
-----Original Message-----
From: Daniel Wagner <dwagner@suse.de>
Sent: Wednesday, 3 April 2024 16:52
To: linux-nvme@lists.infradead.org; Nilay Shroff <nilay@linux.ibm.com>
Cc: Daniel Wagner <dwagner@suse.de>; Engel, Amit <Amit.Engel@Dell.com>; kbusch@kernel.org; gjoyce@ibm.com; Engel, Amit <Amit.Engel@Dell.com>
Subject: Re: [PATCH] fabrics : allow host to create duplicate connections to target


[EXTERNAL EMAIL]


On Wed, 03 Apr 2024 19:04:16 +0530, Nilay Shroff wrote:
> Apparently the nvmf connect code doesn't allow creating duplicate
> connections from a host to the same target even though user specifies
> option "--duplicate-connect" or "-D".
> This patch help fix this issue.
>
>

Applied, thanks!

[1/1] fabrics : allow host to create duplicate connections to target
      commit: fd8ecb054ce53acae504e54666bec6c9976a82dd

Best regards,
--
Daniel Wagner <dwagner@suse.de>


      reply	other threads:[~2024-04-03 16:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03 13:34 [PATCH] fabrics : allow host to create duplicate connections to target Nilay Shroff
2024-04-03 13:51 ` Daniel Wagner
2024-04-03 16:43   ` Engel, Amit [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=CO1PR19MB4885EF4B56B817B4B1C3FB24EE3D2@CO1PR19MB4885.namprd19.prod.outlook.com \
    --to=amit.engel@dell.com \
    --cc=dwagner@suse.de \
    --cc=gjoyce@ibm.com \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=nilay@linux.ibm.com \
    /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).