From: kbuild test robot <fengguang.wu@intel.com>
To: Salil Mehta <salil.mehta@huawei.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org,
Yisen Zhuang <yisen.zhuang@huawei.com>,
Peng Li <lipeng321@huawei.com>,
Fuyun Liang <liangfuyun1@huawei.com>,
Jian Shen <shenjian15@huawei.com>,
Yunsheng Lin <linyunsheng@huawei.com>,
linux-kernel@vger.kernel.org
Subject: [RFC PATCH net-next] net: hns3: hclge_inform_reset_assert_to_vf() can be static
Date: Fri, 23 Mar 2018 05:31:07 +0800 [thread overview]
Message-ID: <20180322213107.GA29844@roam> (raw)
In-Reply-To: <201803230525.jlwCIx4C%fengguang.wu@intel.com>
Fixes: 2bfbd35d8ecd ("net: hns3: Changes required in PF mailbox to support VF reset")
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
hclge_mbx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_mbx.c b/drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_mbx.c
index 3901333..a6f7ffa 100644
--- a/drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_mbx.c
+++ b/drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_mbx.c
@@ -79,7 +79,7 @@ static int hclge_send_mbx_msg(struct hclge_vport *vport, u8 *msg, u16 msg_len,
return status;
}
-int hclge_inform_reset_assert_to_vf(struct hclge_vport *vport)
+static int hclge_inform_reset_assert_to_vf(struct hclge_vport *vport)
{
u8 msg_data[2];
u8 dest_vfid;
next prev parent reply other threads:[~2018-03-22 21:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 21:31 [net-next:master 1115/1116] drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_mbx.c:82:5: sparse: symbol 'hclge_inform_reset_assert_to_vf' was not declared. Should it be static? kbuild test robot
2018-03-22 21:31 ` kbuild test robot [this message]
2018-03-23 17:18 ` [RFC PATCH net-next] net: hns3: hclge_inform_reset_assert_to_vf() can be static David Miller
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=20180322213107.GA29844@roam \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=liangfuyun1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linyunsheng@huawei.com \
--cc=lipeng321@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=salil.mehta@huawei.com \
--cc=shenjian15@huawei.com \
--cc=yisen.zhuang@huawei.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).