From: Roman Bolshakov <r.bolshakov@yadro.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: <linux-scsi@vger.kernel.org>,
<GR-QLogic-Storage-Upstream@marvell.com>,
<target-devel@vger.kernel.org>, <linux@yadro.com>,
Quinn Tran <qutran@marvell.com>, Arun Easi <aeasi@marvell.com>,
Nilesh Javali <njavali@marvell.com>,
Bart Van Assche <bvanassche@acm.org>,
Daniel Wagner <dwagner@suse.de>,
Himanshu Madhani <himanshu.madhani@oracle.com>,
Martin Wilck <mwilck@suse.com>, <stable@vger.kernel.org>
Subject: Re: [PATCH] scsi: qla2xxx: Keep initiator ports after RSCN
Date: Fri, 5 Jun 2020 17:23:11 +0300 [thread overview]
Message-ID: <20200605142311.GC56901@SPB-NB-133.local> (raw)
In-Reply-To: <yq11rmx9b9w.fsf@ca-mkp.ca.oracle.com>
On Tue, Jun 02, 2020 at 09:42:06PM -0400, Martin K. Petersen wrote:
>
> Roman,
>
> > The driver performs SCR (state change registration) in all modes
> > including pure target mode.
>
> What is the current status of this patch? There was a bunch of going
> back and forth wrt. whether this was the correct approach.
>
> Thanks!
>
Hi Martin,
The patch has a logic error that prevents session deletion if N_Port ID
was changed after fabric rescan and shouldn't be merged IMO. I'll send a
correct v2 shortly.
Thanks,
Roman
prev parent reply other threads:[~2020-06-05 14:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 18:31 [PATCH] scsi: qla2xxx: Keep initiator ports after RSCN Roman Bolshakov
2020-05-18 22:40 ` Himanshu Madhani
2020-05-18 23:22 ` Roman Bolshakov
2020-05-26 19:17 ` Martin Wilck
2020-05-19 8:46 ` Martin Wilck
2020-05-21 15:17 ` Roman Bolshakov
2020-05-26 19:21 ` Martin Wilck
2020-06-03 1:42 ` Martin K. Petersen
2020-06-05 14:23 ` Roman Bolshakov [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=20200605142311.GC56901@SPB-NB-133.local \
--to=r.bolshakov@yadro.com \
--cc=GR-QLogic-Storage-Upstream@marvell.com \
--cc=aeasi@marvell.com \
--cc=bvanassche@acm.org \
--cc=dwagner@suse.de \
--cc=himanshu.madhani@oracle.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@yadro.com \
--cc=martin.petersen@oracle.com \
--cc=mwilck@suse.com \
--cc=njavali@marvell.com \
--cc=qutran@marvell.com \
--cc=stable@vger.kernel.org \
--cc=target-devel@vger.kernel.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).