From: Mukesh Ojha <mojha@codeaurora.org>
To: Ding Xiang <dingxiang@cmss.chinamobile.com>,
QLogic-Storage-Upstream@qlogic.com, jejb@linux.ibm.com,
martin.petersen@oracle.com
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: bnx2fc: remove unneeded variable
Date: Fri, 29 Mar 2019 12:40:08 +0530 [thread overview]
Message-ID: <bde8b876-eda6-b23b-5401-cd07015fd767@codeaurora.org> (raw)
In-Reply-To: <1553829852-16525-1-git-send-email-dingxiang@cmss.chinamobile.com>
On 3/29/2019 8:54 AM, Ding Xiang wrote:
> "rc" is unneeded,just return SUCCESS
"rc variable is not needed in `bnx2fc_abts_cleanup`. Fix this by
removing it ."
Reviewed-by: Mukesh Ojha <mojha@codeaurora.org>
-Mukesh
>
> Signed-off-by: Ding Xiang <dingxiang@cmss.chinamobile.com>
> ---
> drivers/scsi/bnx2fc/bnx2fc_io.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/scsi/bnx2fc/bnx2fc_io.c b/drivers/scsi/bnx2fc/bnx2fc_io.c
> index bc9f2a2..8def63c 100644
> --- a/drivers/scsi/bnx2fc/bnx2fc_io.c
> +++ b/drivers/scsi/bnx2fc/bnx2fc_io.c
> @@ -1083,7 +1083,6 @@ int bnx2fc_eh_device_reset(struct scsi_cmnd *sc_cmd)
> static int bnx2fc_abts_cleanup(struct bnx2fc_cmd *io_req)
> {
> struct bnx2fc_rport *tgt = io_req->tgt;
> - int rc = SUCCESS;
> unsigned int time_left;
>
> io_req->wait_for_comp = 1;
> @@ -1110,7 +1109,7 @@ static int bnx2fc_abts_cleanup(struct bnx2fc_cmd *io_req)
> kref_put(&io_req->refcount, bnx2fc_cmd_release);
>
> spin_lock_bh(&tgt->tgt_lock);
> - return rc;
> + return SUCCESS;
> }
>
> /**
next prev parent reply other threads:[~2019-03-29 7:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 3:24 [PATCH] scsi: bnx2fc: remove unneeded variable Ding Xiang
2019-03-29 4:13 ` Manish Rangankar
2019-03-29 7:10 ` Mukesh Ojha [this message]
2019-03-29 14:17 ` 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=bde8b876-eda6-b23b-5401-cd07015fd767@codeaurora.org \
--to=mojha@codeaurora.org \
--cc=QLogic-Storage-Upstream@qlogic.com \
--cc=dingxiang@cmss.chinamobile.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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;
as well as URLs for NNTP newsgroup(s).