case NETDEV_FEAT_CHANGE: bond_compute_features(bond); break;
static int bond_slave_netdev_event(unsigned long event, struct net_device *slave_dev){	struct net_device *bond_dev = slave_dev->master;	switch (event) {	case NETDEV_UNREGISTER:		if (bond_dev) {			bond_release(bond_dev, slave_dev);		}		break;	case NETDEV_CHANGE:		/*		 * TODO: is this what we get if somebody		 * sets up a hierarchical bond, then rmmod's		 * one of the slave bonding devices?		 */		break;	case NETDEV_DOWN:		/*		 * ... Or is it this?		 */		break;	case NETDEV_CHANGEMTU:		/*		 * TODO: Should slaves be allowed to		 * independently alter their MTU?  For		 * an active-backup bond, slaves need		 * not be the same type of device, so		 * MTUs may vary.  For other modes,		 * slaves arguably should have the		 * same MTUs. To do this, we'd need to		 * take over the slave's change_mtu		 * function for the duration of their		 * servitude.		 */		break;	case NETDEV_CHANGENAME:		/*		 * TODO: handle changing the primary's name		 */		break;	default:		break;	}	return NOTIFY_DONE;}