Le mardi 17 mai 2011 Ã 14:16 +0400, Vasiliy Kulikov a Ãcrit : > On Mon, May 16, 2011 at 15:38 -0400, David Miller wrote: > > From: Randy Dunlap <randy.dunlap@xxxxxxxxxx> > > Date: Mon, 16 May 2011 12:35:34 -0700 > > > > > On Mon, 16 May 2011 15:10:19 +1000 Stephen Rothwell wrote: > > > when CONFIG_PROC_SYSCTL is not enabled: > > > > > > ping.c:(.text+0x52af3): undefined reference to `inet_get_ping_group_range_net' > > > > Vasiliy, please fix this. > > I wonder whether there is any way to test such unusual configurations? > Only randconfig or are there any (partly-)automated tools for it? > > > [PATCH] net: ping: fix build failure > > If CONFIG_PROC_SYSCTL=n the building process fails: > > ping.c:(.text+0x52af3): undefined reference to `inet_get_ping_group_range_net' > > Moved inet_get_ping_group_range_net() to ping.c. > > Reported-by: Randy Dunlap <randy.dunlap@xxxxxxxxxx> > Signed-off-by: Vasiliy Kulikov <segoon@xxxxxxxxxxxx> Acked-by: Eric Dumazet <eric.dumazet@xxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
