From: zhengyongjun <zhengyongjun3@huawei.com>
To: "davem@davemloft.net" <davem@davemloft.net>,
"kuba@kernel.org" <kuba@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "jdmason@kudzu.us" <jdmason@kudzu.us>
Subject: 答复: [PATCH net-next] net: vxge: Remove unused variable
Date: Tue, 1 Jun 2021 07:56:07 +0000 [thread overview]
Message-ID: <937ae366ecb54612a05fec858a3b5418@huawei.com> (raw)
In-Reply-To: <20210601074744.4079327-1-zhengyongjun3@huawei.com>
This patch should meld into patch I send before, so please ignore this patch, thank you :)
-----邮件原件-----
发件人: zhengyongjun
发送时间: 2021年6月1日 15:48
收件人: davem@davemloft.net; kuba@kernel.org; netdev@vger.kernel.org; linux-kernel@vger.kernel.org
抄送: jdmason@kudzu.us; zhengyongjun <zhengyongjun3@huawei.com>
主题: [PATCH net-next] net: vxge: Remove unused variable
Removes this annoying warning:
drivers/net/ethernet/neterion/vxge/vxge-main.c:1609:22: warning: unused variable ‘status’ [-Wunused-variable]
1609 | enum vxge_hw_status status;
Signed-off-by: Zheng Yongjun <zhengyongjun3@huawei.com>
---
drivers/net/ethernet/neterion/vxge/vxge-main.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/net/ethernet/neterion/vxge/vxge-main.c b/drivers/net/ethernet/neterion/vxge/vxge-main.c
index 21bc4d6662e4..297bce5f635f 100644
--- a/drivers/net/ethernet/neterion/vxge/vxge-main.c
+++ b/drivers/net/ethernet/neterion/vxge/vxge-main.c
@@ -1606,7 +1606,6 @@ static void vxge_config_ci_for_tti_rti(struct vxgedev *vdev)
static int do_vxge_reset(struct vxgedev *vdev, int event) {
- enum vxge_hw_status status;
int ret = 0, vp_id, i;
vxge_debug_entryexit(VXGE_TRACE, "%s:%d", __func__, __LINE__);
--
2.25.1
next prev parent reply other threads:[~2021-06-01 7:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 7:47 [PATCH net-next] net: vxge: Remove unused variable Zheng Yongjun
2021-06-01 7:56 ` zhengyongjun [this message]
2021-06-01 9:22 ` kernel test robot
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=937ae366ecb54612a05fec858a3b5418@huawei.com \
--to=zhengyongjun3@huawei.com \
--cc=davem@davemloft.net \
--cc=jdmason@kudzu.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).