linux-kernel - Re: [PATCH] staging: lustre: fix sparse warnings for undeclared symbols

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20140602121918.GZ15585@mwanda>
Date:	Mon, 2 Jun 2014 15:19:18 +0300
From:	Dan Carpenter <dan.carpenter@...cle.com>
To:	John Church <sleeveroller@...il.com>
Cc:	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
Subject: Re: [PATCH] staging: lustre: fix sparse warnings for undeclared
 symbols

On Mon, Jun 02, 2014 at 01:03:48PM +0100, John Church wrote:
> 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?
> 

Why not just make them static?  They don't seem to be used outside of
that file.  What am I missing?

regards,
dan carpenter

--
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/