All of lore.kernel.org
 help / color / mirror / Atom feed
From: Devale, Sindhu <sindhu.devale@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [RFC PATCH jkirsher-next-queue] i40iw/i40e: i40iw_open_inc_ref() can be static
Date: Mon, 21 May 2018 23:51:48 +0000	[thread overview]
Message-ID: <2A835467-3A26-4701-BCD8-C3DF81548F4F@intel.com> (raw)
In-Reply-To: <20180521195100.GA37206@lkp-sb05>

ACK.

Thank you,
Sindhu





Fixes: 34a1361d548d ("i40iw/i40e: Remove link dependency on i40e")
Signed-off-by: kbuild test robot <fengguang.wu@intel.com>
---
 i40iw_main.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/infiniband/hw/i40iw/i40iw_main.c b/drivers/infiniband/hw/i40iw/i40iw_main.c
index 65e1269..f4c5be1 100644
--- a/drivers/infiniband/hw/i40iw/i40iw_main.c
+++ b/drivers/infiniband/hw/i40iw/i40iw_main.c
@@ -107,7 +107,7 @@ static struct notifier_block i40iw_netdevice_notifier = {
 /**
  * i40iw_open_inc_ref - Increment ref count for a open
  */
-void i40iw_open_inc_ref(void)
+static void i40iw_open_inc_ref(void)
 {
 	atomic_inc(&peer_drv.peer.ref_count);
 }
@@ -115,7 +115,7 @@ void i40iw_open_inc_ref(void)
 /**
  * i40iw_open_dec_ref - Decrement ref count for a open
  */
-void i40iw_open_dec_ref(void)
+static void i40iw_open_dec_ref(void)
 {
 	struct i40iw_peer *peer;
 


      reply	other threads:[~2018-05-21 23:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-21 19:51 [Intel-wired-lan] [jkirsher-next-queue:dev-queue 25/25] drivers/infiniband/hw/i40iw/i40iw_main.c:110:6: sparse: symbol 'i40iw_open_inc_ref' was not declared. Should it be static? kbuild test robot
2018-05-21 19:51 ` [Intel-wired-lan] [RFC PATCH jkirsher-next-queue] i40iw/i40e: i40iw_open_inc_ref() can be static kbuild test robot
2018-05-21 23:51   ` Devale, Sindhu [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=2A835467-3A26-4701-BCD8-C3DF81548F4F@intel.com \
    --to=sindhu.devale@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.