linux-kernel - [PATCH amirv] IB/ipoib: Prepare the napi in the RX flow [ib-next: ipoib_rx

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20150325155333.GA54248@lkp-sb04>
Date:	Wed, 25 Mar 2015 23:53:33 +0800
From:	kbuild test robot <fengguang.wu@...el.com>
To:	Erez Shitrit <erezsh@...lanox.com>
Cc:	kbuild-all@...org, Roland Dreier <roland@...nel.org>,
	Sean Hefty <sean.hefty@...el.com>,
	Hal Rosenstock <hal.rosenstock@...il.com>,
	Doug Ledford <dledford@...hat.com>,
	Alex Estrin <alex.estrin@...el.com>,
	Or Gerlitz <ogerlitz@...lanox.com>, linux-rdma@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: [PATCH amirv] IB/ipoib: Prepare the napi in the RX flow [ib-next:
 ipoib_rx_poll() can be static


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

diff --git a/drivers/infiniband/ulp/ipoib/ipoib_ib.c b/drivers/infiniband/ulp/ipoib/ipoib_ib.c
index af52a01..8f31a93 100644
--- a/drivers/infiniband/ulp/ipoib/ipoib_ib.c
+++ b/drivers/infiniband/ulp/ipoib/ipoib_ib.c
@@ -375,7 +375,7 @@ static int poll_tx(struct ipoib_dev_priv *priv)
 	return n == MAX_SEND_CQE;
 }
 
-int ipoib_rx_poll(struct napi_struct *napi, int budget)
+static int ipoib_rx_poll(struct napi_struct *napi, int budget)
 {
 	struct ipoib_dev_priv *priv = container_of(napi, struct ipoib_dev_priv, napi_rx);
 	struct net_device *dev = priv->dev;
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/