[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CADvbK_fbCXbWnhtA9na-ajz5_se4d3d-xEH9PE3d7a9=G-RdDA@mail.gmail.com>
Date: Mon, 23 Oct 2017 23:15:14 +0800
From: Xin Long <lucien.xin@...il.com>
To: kbuild test robot <lkp@...el.com>
Cc: kbuild-all@...org, network dev <netdev@...r.kernel.org>,
davem <davem@...emloft.net>, Jiri Pirko <jiri@...nulli.us>
Subject: Re: [PATCHv2 net-next 3/3] bonding: remove rtmsg_ifinfo called after bond_lower_state_changed
On Mon, Oct 23, 2017 at 10:44 PM, kbuild test robot <lkp@...el.com> wrote:
> Hi Xin,
>
> [auto build test ERROR on net-next/master]
>
> url: https://github.com/0day-ci/linux/commits/Xin-Long/bonding-void-calling-rtmsg_ifinfo-for-netlink-notifications/20171023-203332
> config: x86_64-rhel (attached as .config)
> compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> All errors (new ones prefixed by >>):
>
>>> ERROR: "rtmsg_ifinfo" [net/bridge/bridge.ko] undefined!
sorry, didn't notice bridge is still using rtmsg_ifinfo.
rtmsg_ifinfo actually is no need to be called in br_del_if(),
since patch:
dc709f3 rtnetlink: bring NETDEV_CHANGEUPPER event process back in
rtnetlink_event
I will propose another patch to remove this.
for this bonding one, I will post v3 without removing rtmsg_ifinfo
export first.
Powered by blists - more mailing lists