Hi, The cause of the problem in net tree (but **not** net-next tree) is: commit 3ec8e9f085bcaef0de1077f555c2c5102c223390 "bridge: Correctly unregister MDB rtnetlink handlers" and it is fixed by a patch from me, for the net tree, from yesterday. see: http://www.spinics.net/lists/netdev/msg221168.html probably this patch, which was applied to net, was not pulled yet. I believe that since the commit above was not to net-next, this problem is not observed in your tree. Rami Rosen http://ramirose.wix.com/ramirosen On Fri, Jan 4, 2013 at 9:27 PM, Stephen Hemminger <shemminger@xxxxxxxxxx> wrote: > On Fri, 04 Jan 2013 11:11:51 -0800 > Randy Dunlap <rdunlap@xxxxxxxxxxxxx> wrote: > >> On 01/03/13 20:28, Stephen Rothwell wrote: >> > Hi all, >> > >> > Changes since 20130103: >> > >> >> on i386 and x86_64: >> >> CC net/bridge/br_netlink.o >> net/bridge/br_netlink.c: In function 'br_netlink_init': >> net/bridge/br_netlink.c:307:2: error: implicit declaration of function 'br_mdb_init' [-Werror=implicit-function-declaration] >> net/bridge/br_netlink.c:314:2: error: implicit declaration of function 'br_mdb_uninit' [-Werror=implicit-function-declaration] >> cc1: some warnings being treated as errors >> make[3]: *** [net/bridge/br_netlink.o] Error 1 >> >> >> Full randconfig file is attached. >> >> > > Problem not observed with current net-next and your configuration. > Probably already fixed. > -- > To unsubscribe from this list: send the line "unsubscribe netdev" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- 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
