Jay Vosburgh wrote:
Or Gerlitz <[EMAIL PROTECTED]> wrote:
On 9/26/06, Jay Vosburgh <[EMAIL PROTECTED]> wrote:
Or Gerlitz <[EMAIL PROTECTED]> wrote:
[...]
+ bond->dev->mtu = new_active->dev->mtu;
This won't generate a NETDEV_CHANGEMTU notifier event.
What is actua
Or Gerlitz <[EMAIL PROTECTED]> wrote:
>On 9/26/06, Jay Vosburgh <[EMAIL PROTECTED]> wrote:
>> Or Gerlitz <[EMAIL PROTECTED]> wrote:
>> [...]
>> + bond->dev->mtu = new_active->dev->mtu;
>>
>> This won't generate a NETDEV_CHANGEMTU notifier event.
>
>What is actually the t
On 9/26/06, Jay Vosburgh <[EMAIL PROTECTED]> wrote:
Or Gerlitz <[EMAIL PROTECTED]> wrote:
[...]
+ bond->dev->mtu = new_active->dev->mtu;
This won't generate a NETDEV_CHANGEMTU notifier event.
What is actually the trigger for the event with the current impl? is
the co
Or Gerlitz <[EMAIL PROTECTED]> wrote:
[...]
+ bond->dev->mtu = new_active->dev->mtu;
This won't generate a NETDEV_CHANGEMTU notifier event.
[...]
>+ /* bonding netdevices are created with ether_setup, so when the
>+ * slave type is not ARPHRD_
Signed-off-by: Or Gerlitz <[EMAIL PROTECTED]>
Index: net-2.6.19/drivers/net/bonding/bond_main.c
===
--- net-2.6.19.orig/drivers/net/bonding/bond_main.c 2006-09-20
14:40:13.0 +0300
+++ net-2.6.19/drivers/net/bonding/bond_m
