From: James Smart <jsmart2021@gmail.com>
To: cgel.zte@gmail.com, martin.petersen@oracle.com
Cc: james.smart@broadcom.com, dick.kennedy@broadcom.com,
jejb@linux.ibm.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org,
ye xingchen <ye.xingchen@zte.com.cn>,
Zeal Robot <zealci@zte.com.cn>
Subject: Re: [PATCH linux-next] scsi: lpfc: Remove the unneeded result variable
Date: Wed, 24 Aug 2022 07:14:23 -0700 [thread overview]
Message-ID: <9caed19e-ec83-92d3-cc86-586cc01f2fee@gmail.com> (raw)
In-Reply-To: <20220824075017.221244-1-ye.xingchen@zte.com.cn>
On 8/24/2022 12:50 AM, cgel.zte@gmail.com wrote:
> From: ye xingchen <ye.xingchen@zte.com.cn>
>
> Return the value from lpfc_sli4_issue_wqe() directly instead of storing it
> in another redundant variable.
>
> Reported-by: Zeal Robot <zealci@zte.com.cn>
> Signed-off-by: ye xingchen <ye.xingchen@zte.com.cn>
> ---
> drivers/scsi/lpfc/lpfc_sli.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/scsi/lpfc/lpfc_sli.c b/drivers/scsi/lpfc/lpfc_sli.c
> index 608016725db9..1298cea81396 100644
> --- a/drivers/scsi/lpfc/lpfc_sli.c
> +++ b/drivers/scsi/lpfc/lpfc_sli.c
> @@ -10322,12 +10322,10 @@ static int
> __lpfc_sli_issue_fcp_io_s4(struct lpfc_hba *phba, uint32_t ring_number,
> struct lpfc_iocbq *piocb, uint32_t flag)
> {
> - int rc;
> struct lpfc_io_buf *lpfc_cmd = piocb->io_buf;
>
> lpfc_prep_embed_io(phba, lpfc_cmd);
> - rc = lpfc_sli4_issue_wqe(phba, lpfc_cmd->hdwq, piocb);
> - return rc;
> + return lpfc_sli4_issue_wqe(phba, lpfc_cmd->hdwq, piocb);
> }
>
> void
Thanks
Reviewed-by: James Smart <jsmart2021@gmail.com>
-- james
next prev parent reply other threads:[~2022-08-24 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 7:50 [PATCH linux-next] scsi: lpfc: Remove the unneeded result variable cgel.zte
2022-08-24 14:14 ` James Smart [this message]
2022-09-01 4:39 ` 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=9caed19e-ec83-92d3-cc86-586cc01f2fee@gmail.com \
--to=jsmart2021@gmail.com \
--cc=cgel.zte@gmail.com \
--cc=dick.kennedy@broadcom.com \
--cc=james.smart@broadcom.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ye.xingchen@zte.com.cn \
--cc=zealci@zte.com.cn \
/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.