From: kbuild test robot <fengguang.wu@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [RFC PATCH jkirsher-next-queue] i40e: i40e_find_vsi_from_seid() can be static
Date: Sat, 13 Jan 2018 07:19:08 +0800 [thread overview]
Message-ID: <20180112231907.GA40910@xian> (raw)
In-Reply-To: <201801130740.nIajnAAm%fengguang.wu@intel.com>
Fixes: 5a2f5288e803 ("i40e: Add and delete cloud filter")
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
i40e_virtchnl_pf.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.c b/drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.c
index d0c8183..04120bc 100644
--- a/drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.c
+++ b/drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.c
@@ -3054,7 +3054,7 @@ static int i40e_validate_cloud_filter(struct i40e_vf *vf,
* @vf: pointer to the VF info
* @seid - seid of the vsi it is searching for
**/
-struct i40e_vsi *i40e_find_vsi_from_seid(struct i40e_vf *vf, u16 seid)
+static struct i40e_vsi *i40e_find_vsi_from_seid(struct i40e_vf *vf, u16 seid)
{
struct i40e_pf *pf = vf->pf;
struct i40e_vsi *vsi = NULL;
@@ -3074,7 +3074,7 @@ struct i40e_vsi *i40e_find_vsi_from_seid(struct i40e_vf *vf, u16 seid)
*
* This function deletes all cloud filters
**/
-void i40e_del_all_cloud_filters(struct i40e_vf *vf)
+static void i40e_del_all_cloud_filters(struct i40e_vf *vf)
{
struct i40e_cloud_filter *cfilter = NULL;
struct i40e_pf *pf = vf->pf;
prev parent reply other threads:[~2018-01-12 23:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 23:19 [Intel-wired-lan] [jkirsher-next-queue:dev-queue 109/109] drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.c:3017:43: sparse: restricted __be16 degrades to integer kbuild test robot
2018-01-12 23:19 ` kbuild test robot [this message]
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=20180112231907.GA40910@xian \
--to=fengguang.wu@intel.com \
--cc=intel-wired-lan@osuosl.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 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.