All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Or Gerlitz <ogerlitz@mellanox.com>
Cc: kbuild-all@01.org, Ido Shamay <idos@mellanox.com>,
	Amir Vadai <amirv@mellanox.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH jkirsher-next-queue] net/mlx4_en: mlx4_en_set_tx_maxrate() can be static
Date: Thu, 19 Mar 2015 08:51:27 +0800	[thread overview]
Message-ID: <20150319005127.GA57239@snb> (raw)
In-Reply-To: <201503190816.FI64cKgW%fengguang.wu@intel.com>


Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
 en_netdev.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/ethernet/mellanox/mlx4/en_netdev.c b/drivers/net/ethernet/mellanox/mlx4/en_netdev.c
index d8dc3f9..763ba26 100644
--- a/drivers/net/ethernet/mellanox/mlx4/en_netdev.c
+++ b/drivers/net/ethernet/mellanox/mlx4/en_netdev.c
@@ -2379,7 +2379,7 @@ static netdev_features_t mlx4_en_features_check(struct sk_buff *skb,
 }
 #endif
 
-int mlx4_en_set_tx_maxrate(struct net_device *dev, int queue_index, u32 maxrate)
+static int mlx4_en_set_tx_maxrate(struct net_device *dev, int queue_index, u32 maxrate)
 {
 	struct mlx4_en_priv *priv = netdev_priv(dev);
 	struct mlx4_en_tx_ring *tx_ring = priv->tx_ring[queue_index];

  reply	other threads:[~2015-03-19  0:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-19  0:51 [jkirsher-next-queue:dev-queue 828/842] drivers/net/ethernet/mellanox/mlx4/en_netdev.c:2382:5: sparse: symbol 'mlx4_en_set_tx_maxrate' was not declared. Should it be static? kbuild test robot
2015-03-19  0:51 ` kbuild test robot [this message]
2015-03-19  3:21   ` [PATCH jkirsher-next-queue] net/mlx4_en: mlx4_en_set_tx_maxrate() 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=20150319005127.GA57239@snb \
    --to=fengguang.wu@intel.com \
    --cc=amirv@mellanox.com \
    --cc=idos@mellanox.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=ogerlitz@mellanox.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.