From: Muneendra Kumar M <muneendra.kumar@broadcom.com>
To: Hannes Reinecke <hare@suse.de>,
linux-scsi@vger.kernel.org, michael.christie@oracle.com
Cc: jsmart2021@gmail.com, emilne@redhat.com, mkumar@redhat.com
Subject: RE: [PATCH v7 3/5] scsi_transport_fc: Added a new rport state FC_PORTSTATE_MARGINAL
Date: Tue, 17 Nov 2020 13:13:37 +0530 [thread overview]
Message-ID: <4bf70107a0f27dd0e88fc4166c196101@mail.gmail.com> (raw)
In-Reply-To: <4e638c14-faf4-0a63-a715-86e9baabedda@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]
Hi Hannes,
Thanks for the review.
> + { FC_PORTSTATE_LOOPBACK, "Loopback", 8 },
> + { FC_PORTSTATE_DELETED, "Deleted", 7 },
> + { FC_PORTSTATE_MARGINAL, "Marginal", 8 },
>Why did you append the length of the string here?
>This doesn't have anything to do with this patch, but rather is an
>improvement/modification of the original code, and should be delegated to a
>separate patch.
[Muneendra] fc_enum_name_match needs the string length for validation.
get_fc_port_state_match will use this as part of setting the port_state in
sysfs for validation(next patch 4/5).
> };
> fc_enum_name_search(port_state, fc_port_state, fc_port_state_names)
> +fc_enum_name_match(port_state, fc_port_state, fc_port_state_names)
> #define FC_PORTSTATE_MAX_NAMELEN 20
>
....
...
>Other than that:
>Reviewed-by: Hannes Reinecke <hare@suse.de>
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg HRB 36809 (AG
Nürnberg), Geschäftsführer: Felix Imendörffer
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4177 bytes --]
next prev parent reply other threads:[~2020-11-17 7:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 4:58 [PATCH v7 0/5] scsi: Support to handle Intermittent errors Muneendra
2020-11-11 4:58 ` [PATCH v7 1/5] scsi: Added a new error code DID_TRANSPORT_MARGINAL in scsi.h Muneendra
2020-11-16 8:16 ` Hannes Reinecke
2020-11-23 19:45 ` Ewan D. Milne
2020-11-24 17:42 ` Himanshu Madhani
2020-11-11 4:58 ` [PATCH v7 2/5] scsi: No retries on abort success Muneendra
2020-11-16 8:22 ` Hannes Reinecke
2020-11-23 19:45 ` Ewan D. Milne
2020-11-24 17:43 ` Himanshu Madhani
2020-11-11 4:58 ` [PATCH v7 3/5] scsi_transport_fc: Added a new rport state FC_PORTSTATE_MARGINAL Muneendra
2020-11-16 8:19 ` Hannes Reinecke
2020-11-17 7:43 ` Muneendra Kumar M [this message]
2020-11-23 20:01 ` Ewan D. Milne
2020-11-23 19:47 ` Ewan D. Milne
2020-11-24 17:43 ` Himanshu Madhani
2020-11-11 4:58 ` [PATCH v7 4/5] scsi_transport_fc: Added store fucntionality to set the rport port_state using sysfs Muneendra
2020-11-16 8:20 ` Hannes Reinecke
2020-11-23 19:47 ` Ewan D. Milne
2020-11-24 17:44 ` Himanshu Madhani
2020-11-11 4:58 ` [PATCH v7 5/5] scsi:lpfc: Added support for eh_should_retry_cmd Muneendra
2020-11-16 8:23 ` Hannes Reinecke
2020-11-23 19:51 ` Ewan D. Milne
2020-11-23 19:48 ` Ewan D. Milne
2020-11-24 17:46 ` Himanshu Madhani
2020-12-08 5:00 ` [PATCH v7 0/5] scsi: Support to handle Intermittent errors Muneendra Kumar M
2020-12-08 5:14 ` 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=4bf70107a0f27dd0e88fc4166c196101@mail.gmail.com \
--to=muneendra.kumar@broadcom.com \
--cc=emilne@redhat.com \
--cc=hare@suse.de \
--cc=jsmart2021@gmail.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michael.christie@oracle.com \
--cc=mkumar@redhat.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