From: John Church <sleeveroller@gmail.com>
To: gregkh@linuxfoundation.org, lisa@xenapiadmin.com,
bergwolf@gmail.com, andreas.dilger@intel.com,
oleg.drokin@intel.com, doug.s.oucharek@intel.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Cc: John Church <sleeveroller@gmail.com>
Subject: [PATCH] staging: lustre: fix sparse warnings for undeclared symbols
Date: Mon, 2 Jun 2014 14:31:10 +0100 [thread overview]
Message-ID: <1401715870-14690-1-git-send-email-sleeveroller@gmail.com> (raw)
This patch fixes the following sparse warnings for drivers/staging/lustre/lnet/lnet/router.c:
router.c:139:1: warning: symbol 'lnet_ni_notify_locked' was not declared. Should it be static?
router.c:277:1: warning: symbol 'lnet_add_route_to_rnet' was not declared. Should it be static?
Signed-off-by: John Church <sleeveroller@gmail.com>
---
drivers/staging/lustre/lnet/lnet/router.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/lustre/lnet/lnet/router.c b/drivers/staging/lustre/lnet/lnet/router.c
index 995f509..87e0c3b 100644
--- a/drivers/staging/lustre/lnet/lnet/router.c
+++ b/drivers/staging/lustre/lnet/lnet/router.c
@@ -135,7 +135,7 @@ lnet_notify_locked(lnet_peer_t *lp, int notifylnd, int alive, cfs_time_t when)
CDEBUG(D_NET, "set %s %d\n", libcfs_nid2str(lp->lp_nid), alive);
}
-void
+static void
lnet_ni_notify_locked(lnet_ni_t *ni, lnet_peer_t *lp)
{
int alive;
@@ -273,7 +273,7 @@ static void lnet_shuffle_seed(void)
}
/* NB expects LNET_LOCK held */
-void
+static void
lnet_add_route_to_rnet (lnet_remotenet_t *rnet, lnet_route_t *route)
{
unsigned int len = 0;
--
1.7.10.4
next reply other threads:[~2014-06-02 13:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 13:31 John Church [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-06-16 10:44 [PATCH] staging: lustre: Fix sparse warnings for undeclared symbols Scott Weir
2014-06-02 12:03 [PATCH] staging: lustre: fix " John Church
2014-06-02 12:19 ` Dan Carpenter
2014-06-02 13:14 ` John Church
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=1401715870-14690-1-git-send-email-sleeveroller@gmail.com \
--to=sleeveroller@gmail.com \
--cc=andreas.dilger@intel.com \
--cc=bergwolf@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=doug.s.oucharek@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lisa@xenapiadmin.com \
--cc=oleg.drokin@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox