the variables zero and unres_qlen_max are only used when CONFIG_SYSCTL is defined, otherwise it causes the following sparse warning when we turn on CONFIG_SYSCTL.
Signed-off-by: Cong Ding <ding...@gmail.com> --- net/core/neighbour.c | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/net/core/neighbour.c b/net/core/neighbour.c index 36fc692..4a15278 100644 --- a/net/core/neighbour.c +++ b/net/core/neighbour.c @@ -62,8 +62,10 @@ static void __neigh_notify(struct neighbour *n, int type, int flags); static void neigh_update_notify(struct neighbour *neigh); static int pneigh_ifdown(struct neigh_table *tbl, struct net_device *dev); +#ifdef CONFIG_SYSCTL static int zero; static int unres_qlen_max = INT_MAX / SKB_TRUESIZE(ETH_FRAME_LEN); +#endif static struct neigh_table *neigh_tables; #ifdef CONFIG_PROC_FS -- 1.7.4.5 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
