From: kbuild test robot <fengguang.wu@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [RFC PATCH linux-next] net: __ixgbe_setup_tc() can be static
Date: Fri, 18 Mar 2016 23:44:01 +0800 [thread overview]
Message-ID: <20160318154401.GA62161@cairo> (raw)
In-Reply-To: <201603182332.ZrvaiiNr%fengguang.wu@intel.com>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
ixgbe_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c b/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
index 1ba714e..3339249 100644
--- a/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
+++ b/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
@@ -8200,7 +8200,7 @@ int ixgbe_setup_tc(struct net_device *dev, u8 tc)
return 0;
}
-int __ixgbe_setup_tc(struct net_device *dev, u32 handle, u8 tc)
+static int __ixgbe_setup_tc(struct net_device *dev, u32 handle, u8 tc)
{
/* Only support egress tc setup for now */
if (handle != TC_H_ROOT)
prev parent reply other threads:[~2016-03-18 15:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 15:44 [Intel-wired-lan] [linux-next:master 4836/12950] drivers/net/ethernet/intel/ixgbe/ixgbe_main.c:8203:5: sparse: symbol '__ixgbe_setup_tc' was not declared. Should it be static? kbuild test robot
2016-03-18 15:44 ` 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=20160318154401.GA62161@cairo \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox