From: James.Bottomley@HansenPartnership.com (James Bottomley)
Subject: [PATCH v2 1/6] qla2xxx: Add FC-NVMe port discovery and PRLI handling
Date: Wed, 28 Jun 2017 14:15:45 -0700 [thread overview]
Message-ID: <1498684545.2769.17.camel@HansenPartnership.com> (raw)
In-Reply-To: <20170621204846.21663-2-himanshu.madhani@cavium.com>
On Wed, 2017-06-21@13:48 -0700, Madhani, Himanshu wrote:
> From: Duane Grigsby <duane.grigsby at cavium.com>
>
> Added logic to change the login process into an optional PRIL
> step for FC-NVMe ports as a separate operation, such that we can
> change type to 0x28 (NVMe).
>
> Currently, the driver performs the PLOGI/PRLI together as one
> operation, but if the discovered port is an NVMe port then we
> first issue the PLOGI and then we issue the PRLI. Also, the
> fabric discovery logic was changed to mark each discovered FC
> NVMe port, so that we can register them with the FC-NVMe transport
> later.
>
> Signed-off-by: Darren Trapp <darren.trapp at cavium.com>
> Signed-off-by: Duane Grigsby <duane.grigsby at cavium.com>
> Signed-off-by: Anil Gurumurthy <anil.gurumurhty at cavium.com>
I just got a whole load of bounces from this: you've misspelled Anil's
email address (h and t transposed). ?It looks like a generic cut and
paste, so could you fix it for next time?
Thanks,
James
WARNING: multiple messages have this Message-ID (diff)
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Madhani, Himanshu" <himanshu.madhani@cavium.com>,
martin.petersen@oracle.com
Cc: linux-scsi@vger.kernel.org, darren.trapp@cavium.com,
giridhar.malavali@cavium.com, linux-nvme@lists.infradead.org
Subject: Re: [PATCH v2 1/6] qla2xxx: Add FC-NVMe port discovery and PRLI handling
Date: Wed, 28 Jun 2017 14:15:45 -0700 [thread overview]
Message-ID: <1498684545.2769.17.camel@HansenPartnership.com> (raw)
In-Reply-To: <20170621204846.21663-2-himanshu.madhani@cavium.com>
On Wed, 2017-06-21 at 13:48 -0700, Madhani, Himanshu wrote:
> From: Duane Grigsby <duane.grigsby@cavium.com>
>
> Added logic to change the login process into an optional PRIL
> step for FC-NVMe ports as a separate operation, such that we can
> change type to 0x28 (NVMe).
>
> Currently, the driver performs the PLOGI/PRLI together as one
> operation, but if the discovered port is an NVMe port then we
> first issue the PLOGI and then we issue the PRLI. Also, the
> fabric discovery logic was changed to mark each discovered FC
> NVMe port, so that we can register them with the FC-NVMe transport
> later.
>
> Signed-off-by: Darren Trapp <darren.trapp@cavium.com>
> Signed-off-by: Duane Grigsby <duane.grigsby@cavium.com>
> Signed-off-by: Anil Gurumurthy <anil.gurumurhty@cavium.com>
I just got a whole load of bounces from this: you've misspelled Anil's
email address (h and t transposed). It looks like a generic cut and
paste, so could you fix it for next time?
Thanks,
James
next prev parent reply other threads:[~2017-06-28 21:15 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 20:48 [PATCH v2 0/6] qla2xxx: Add NVMe FC Fabric support in driver Madhani, Himanshu
2017-06-21 20:48 ` Madhani, Himanshu
2017-06-21 20:48 ` [PATCH v2 1/6] qla2xxx: Add FC-NVMe port discovery and PRLI handling Madhani, Himanshu
2017-06-21 20:48 ` Madhani, Himanshu
2017-06-22 6:28 ` Hannes Reinecke
2017-06-22 6:28 ` Hannes Reinecke
2017-06-28 21:15 ` James Bottomley [this message]
2017-06-28 21:15 ` James Bottomley
2017-06-28 21:23 ` Madhani, Himanshu
2017-06-28 21:23 ` Madhani, Himanshu
2017-06-21 20:48 ` [PATCH v2 2/6] qla2xxx: Add FC-NVMe command handling Madhani, Himanshu
2017-06-21 20:48 ` Madhani, Himanshu
2017-06-22 6:28 ` Hannes Reinecke
2017-06-22 6:28 ` Hannes Reinecke
2017-06-21 20:48 ` [PATCH v2 3/6] qla2xxx: Add FC-NVMe F/W initialization and transport registration Madhani, Himanshu
2017-06-21 20:48 ` Madhani, Himanshu
2017-06-22 6:32 ` Hannes Reinecke
2017-06-22 6:32 ` Hannes Reinecke
2017-06-22 9:46 ` Johannes Thumshirn
2017-06-22 9:46 ` Johannes Thumshirn
[not found] ` <2d07d1fd-545b-0308-8a2b-5cfb59cbcf2b@broadcom.com>
2017-06-22 18:53 ` Johannes Thumshirn
2017-06-22 18:53 ` Johannes Thumshirn
2017-06-23 3:16 ` Madhani, Himanshu
2017-06-23 3:16 ` Madhani, Himanshu
2017-06-23 6:28 ` Johannes Thumshirn
2017-06-23 6:28 ` Johannes Thumshirn
2017-06-21 20:48 ` [PATCH v2 4/6] qla2xxx: Send FC4 type NVMe to the management server Madhani, Himanshu
2017-06-21 20:48 ` Madhani, Himanshu
2017-06-22 6:33 ` Hannes Reinecke
2017-06-22 6:33 ` Hannes Reinecke
2017-06-22 9:51 ` Johannes Thumshirn
2017-06-22 9:51 ` Johannes Thumshirn
2017-06-21 20:48 ` [PATCH v2 5/6] qla2xxx: Use FC-NMVe FC4 type for FDMI registration Madhani, Himanshu
2017-06-21 20:48 ` Madhani, Himanshu
2017-06-22 6:33 ` Hannes Reinecke
2017-06-22 6:33 ` Hannes Reinecke
2017-06-22 9:52 ` Johannes Thumshirn
2017-06-22 9:52 ` Johannes Thumshirn
2017-06-21 20:48 ` [PATCH v2 6/6] qla2xxx: Update Driver version to 10.00.00.00-k Madhani, Himanshu
2017-06-21 20:48 ` Madhani, Himanshu
2017-06-22 6:33 ` Hannes Reinecke
2017-06-22 6:33 ` Hannes Reinecke
2017-06-28 1:49 ` [PATCH v2 0/6] qla2xxx: Add NVMe FC Fabric support in driver Martin K. Petersen
2017-06-28 1:49 ` Martin K. Petersen
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=1498684545.2769.17.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.