Netdev List
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: kbuild-internal@linux.intel.com, lkp@eclists.intel.com
Cc: kbuild-all@01.org, netdev@vger.kernel.org
Subject: [RFC PATCH net-next] tipc: tipc_link_is_active() can be static
Date: Sat, 24 Oct 2015 23:11:00 +0800	[thread overview]
Message-ID: <20151024151100.GA46525@lkp-hsx03> (raw)
In-Reply-To: <201510242340.mc7bt8l1%fengguang.wu@intel.com>

TO: "David S. Miller" <davem@davemloft.net>
CC: netdev@vger.kernel.org
CC: Jon Maloy <jon.maloy@ericsson.com>
CC: Ying Xue <ying.xue@windriver.com>
CC: tipc-discussion@lists.sourceforge.net
CC: linux-kernel@vger.kernel.org


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

diff --git a/net/tipc/link.c b/net/tipc/link.c
index 4449fa0..b637276 100644
--- a/net/tipc/link.c
+++ b/net/tipc/link.c
@@ -173,7 +173,7 @@ bool link_is_bc_rcvlink(struct tipc_link *l)
 	return ((l->bc_rcvlink == l) && !link_is_bc_sndlink(l));
 }
 
-int tipc_link_is_active(struct tipc_link *l)
+static int tipc_link_is_active(struct tipc_link *l)
 {
 	return l->active;
 }

  reply	other threads:[~2015-10-24 15:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-24 15:11 [net-next:master 1610/1613] net/tipc/link.c:176:5: sparse: symbol 'tipc_link_is_active' was not declared. Should it be static? kbuild test robot
2015-10-24 15:11 ` kbuild test robot [this message]
2015-10-24 18:49   ` [RFC PATCH net-next] tipc: tipc_link_is_active() can be static Jon Maloy
2015-10-25 13:33   ` David Miller
2015-10-26  1:13     ` Fengguang Wu

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=20151024151100.GA46525@lkp-hsx03 \
    --to=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=kbuild-internal@linux.intel.com \
    --cc=lkp@eclists.intel.com \
    --cc=netdev@vger.kernel.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