| 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
| ||
|
Date: Mon, 2 Jun 2014 13:03:48 +0100 From: John Church <sleeveroller@...il.com> To: gregkh@...uxfoundation.org, lisa@...apiadmin.com, bergwolf@...il.com, andreas.dilger@...el.com, oleg.drokin@...el.com, doug.s.oucharek@...el.com, devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org Cc: John Church <sleeveroller@...il.com> Subject: [PATCH] staging: lustre: fix sparse warnings for undeclared symbols 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@...il.com> --- drivers/staging/lustre/include/linux/lnet/lib-lnet.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/staging/lustre/include/linux/lnet/lib-lnet.h b/drivers/staging/lustre/include/linux/lnet/lib-lnet.h index 856fcfa..143bb3a 100644 --- a/drivers/staging/lustre/include/linux/lnet/lib-lnet.h +++ b/drivers/staging/lustre/include/linux/lnet/lib-lnet.h @@ -650,6 +650,8 @@ extern lnet_ni_t *lnet_net2ni(__u32 net); int lnet_notify(lnet_ni_t *ni, lnet_nid_t peer, int alive, cfs_time_t when); void lnet_notify_locked(lnet_peer_t *lp, int notifylnd, int alive, cfs_time_t when); +void lnet_ni_notify_locked(lnet_ni_t *ni, lnet_peer_t *lp); +void lnet_add_route_to_rnet(lnet_remotenet_t *rnet, lnet_route_t *route); int lnet_add_route(__u32 net, unsigned int hops, lnet_nid_t gateway_nid, unsigned int priority); int lnet_check_routes(void); -- 1.7.10.4 -- 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/
Powered by blists - more mailing lists