From: David Arcari
Date: Mon, 13 Mar 2017 16:30:52 -0400
> Please drop v2 of this patch. We would like to have v1 applied.
Resubmit v1 again if you want me to do this.
On 03/10/2017 04:19 PM, Pavel Belous wrote:
>
>
> On 10.03.2017 17:47, David Arcari wrote:
>> Hi,
>>
>> On 03/09/2017 05:43 PM, Lino Sanfilippo wrote:
>>> Hi,
>>>
>>> On 09.03.2017 22:03, David Arcari wrote:
When the aquantia device mtu is changed the net_device structure is not
updated
On 10.03.2017 17:47, David Arcari wrote:
Hi,
On 03/09/2017 05:43 PM, Lino Sanfilippo wrote:
Hi,
On 09.03.2017 22:03, David Arcari wrote:
When the aquantia device mtu is changed the net_device structure is not
updated. As a result the ip command does not properly reflect the mtu change.
Co
Hi,
On 03/09/2017 05:43 PM, Lino Sanfilippo wrote:
> Hi,
>
> On 09.03.2017 22:03, David Arcari wrote:
>> When the aquantia device mtu is changed the net_device structure is not
>> updated. As a result the ip command does not properly reflect the mtu
>> change.
>>
>> Commit 5513e16421cb incorrec
Hi,
On 09.03.2017 22:03, David Arcari wrote:
> When the aquantia device mtu is changed the net_device structure is not
> updated. As a result the ip command does not properly reflect the mtu change.
>
> Commit 5513e16421cb incorrectly assumed that __dev_set_mtu() was making the
> assignment ndev
On 10.03.2017 00:03, David Arcari wrote:
When the aquantia device mtu is changed the net_device structure is not
updated. As a result the ip command does not properly reflect the mtu change.
Commit 5513e16421cb incorrectly assumed that __dev_set_mtu() was making the
assignment ndev->mtu = new
When the aquantia device mtu is changed the net_device structure is not
updated. As a result the ip command does not properly reflect the mtu change.
Commit 5513e16421cb incorrectly assumed that __dev_set_mtu() was making the
assignment ndev->mtu = new_mtu; This is not true in the case where the
