From: Payal Kshirsagar <payalskshirsagar1234@gmail.com>
To: manishc@marvell.com, GR-Linux-NIC-Dev@marvell.com,
gregkh@linuxfoundation.org, outreachy-kernel@googlegroups.com
Cc: Payal Kshirsagar <payalskshirsagar1234@gmail.com>
Subject: [PATCH 2/4] [Outreachy kernel] staging: qlge: qlge_mpi.c: remove an unneeded variable
Date: Wed, 11 Mar 2020 14:58:13 +0530 [thread overview]
Message-ID: <6f5c42cce80a33a4b638bbb9d3994f85554c9a37.1583918265.git.payalskshirsagar1234@gmail.com> (raw)
In-Reply-To: <cover.1583918265.git.payalskshirsagar1234@gmail.com>
In-Reply-To: <cover.1583918265.git.payalskshirsagar1234@gmail.com>
Remove unneeded temporary local variable, cleanup suggested by coccinelle.
Signed-off-by: Payal Kshirsagar <payalskshirsagar1234@gmail.com>
---
drivers/staging/qlge/qlge_mpi.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/staging/qlge/qlge_mpi.c b/drivers/staging/qlge/qlge_mpi.c
index bb03b2fa7233..eae168e94b82 100644
--- a/drivers/staging/qlge/qlge_mpi.c
+++ b/drivers/staging/qlge/qlge_mpi.c
@@ -90,9 +90,7 @@ int ql_write_mpi_reg(struct ql_adapter *qdev, u32 reg, u32 data)
int ql_soft_reset_mpi_risc(struct ql_adapter *qdev)
{
- int status;
- status = ql_write_mpi_reg(qdev, 0x00001010, 1);
- return status;
+ return ql_write_mpi_reg(qdev, 0x00001010, 1);
}
/* Determine if we are in charge of the firwmare. If
--
2.17.1
next prev parent reply other threads:[~2020-03-11 9:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 9:28 [PATCH 0/4] [Outreachy kernel] staging: qlge: remove unneeded variables Payal Kshirsagar
2020-03-11 9:28 ` [PATCH 1/4] [Outreachy kernel] staging: qlge: qlge_main.c: remove an unneeded variable Payal Kshirsagar
2020-03-11 9:28 ` Payal Kshirsagar [this message]
2020-03-11 9:28 ` [PATCH 3/4] [Outreachy kernel] staging: qlge: qlge_dbg.c: " Payal Kshirsagar
2020-03-11 9:28 ` [PATCH 4/4] [Outreachy kernel] staging: qlge: qlge_ethtool.c: " Payal Kshirsagar
2020-03-11 12:08 ` Stefano Brivio
2020-03-11 12:20 ` Payal Kshirsagar
2020-03-11 12:44 ` Stefano Brivio
2020-03-11 13:46 ` Payal Kshirsagar
2020-03-11 14:31 ` Stefano Brivio
2020-03-11 14:44 ` Payal Kshirsagar
2020-03-11 15:07 ` Julia Lawall
2020-03-11 15:52 ` Payal Kshirsagar
2020-03-11 16:48 ` Stefano Brivio
2020-03-11 17:19 ` Payal Kshirsagar
2020-03-11 20:31 ` Julia Lawall
2020-03-11 23:12 ` Stefano Brivio
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=6f5c42cce80a33a4b638bbb9d3994f85554c9a37.1583918265.git.payalskshirsagar1234@gmail.com \
--to=payalskshirsagar1234@gmail.com \
--cc=GR-Linux-NIC-Dev@marvell.com \
--cc=gregkh@linuxfoundation.org \
--cc=manishc@marvell.com \
--cc=outreachy-kernel@googlegroups.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.