From: Bart Van Assche <bvanassche@acm.org>
To: Himanshu Madhani <hmadhani@marvell.com>
Cc: Roman Bolshakov <r.bolshakov@yadro.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
Quinn Tran <qutran@marvell.com>
Subject: Re: [PATCH] Revert "qla2xxx: Fix Nport ID display value"
Date: Tue, 19 Nov 2019 16:15:04 -0800 [thread overview]
Message-ID: <fa7d57ec-77b3-3397-063e-d949716abaa8@acm.org> (raw)
In-Reply-To: <1dac96c3-54d5-11bf-292b-c25a62a3c919@acm.org>
On 11/13/19 6:34 PM, Bart Van Assche wrote:
> On 2019-11-13 07:29, Himanshu Madhani wrote:
>> On Nov 11, 2019, at 8:48 PM, Bart Van Assche <bvanassche@acm.org> wrote:
>>> Himanshu, can you tell us which adapters and/or firmware versions need
>>> which version of the above code?
>>
>> All adapters with FW v4.4 will behave same. If you are running into issue with P2P connection,
>> it might be something different than specific to this code change. Original code in the driver was not
>> following firmware spec. This code is now used in initiator mode as well due to introduction of
>> FC-NVMe handling in the driver. Also, can you tell me what version of firmware you have on your
>> remote port.
>
> Hi Himanshu,
>
> My test was run on a setup with a single QLE2562 adapter with both FC
> ports connected directly to each other. The kernel driver identifies
> that adapter as follows: ISP2532: PCIe (5.0GT/s x8) @ 0000:00:0a.0 hdma+
> host#=12 fw=8.07.00 (90d5). Please let me know if you need more information.
Ping?
Bart.
next prev parent reply other threads:[~2019-11-20 0:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-09 4:21 [PATCH] Revert "qla2xxx: Fix Nport ID display value" Bart Van Assche
2019-11-11 11:28 ` Roman Bolshakov
2019-11-12 2:48 ` Bart Van Assche
2019-11-13 15:29 ` Himanshu Madhani
2019-11-14 2:34 ` Bart Van Assche
2019-11-20 0:15 ` Bart Van Assche [this message]
2019-11-20 21:39 ` Himanshu Madhani
2019-11-21 3:26 ` Bart Van Assche
2019-12-02 16:40 ` Bart Van Assche
2019-12-02 20:55 ` Roman Bolshakov
2019-12-03 2:34 ` Bart Van Assche
2019-12-04 12:07 ` Roman Bolshakov
2019-12-06 6:03 ` Bart Van Assche
2019-12-09 23:18 ` Martin K. Petersen
2019-12-10 19:38 ` [EXT] " 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=fa7d57ec-77b3-3397-063e-d949716abaa8@acm.org \
--to=bvanassche@acm.org \
--cc=hmadhani@marvell.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=qutran@marvell.com \
--cc=r.bolshakov@yadro.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