-----Original Message-----
From: Haiyang Zhang [mailto:haiyangz@microsoft.com]
Sent: Thursday, October 20, 2016 2:05 PM
To: Jarod Wilson <redacted>; <redacted>
Cc: <redacted>; <redacted>; KY
Srinivasan [off-list ref]; Michael S. Tsirkin [off-list ref];
Shrikrishna Khare [off-list ref]; VMware, Inc. <pv-
drivers@vmware.com>; Wei Liu [off-list ref]; Paul Durrant
[off-list ref]; Kershner, David A
[off-list ref]
Subject: RE: [PATCH net-next v2 6/9] net: use core MTU range checking in virt
drivers
quoted
-----Original Message-----
From: Jarod Wilson [mailto:<redacted>]
Sent: Thursday, October 20, 2016 1:55 PM
To: <redacted>
Cc: Jarod Wilson <redacted>; <redacted>;
virtualization@lists.linux-foundation.org; KY Srinivasan
[off-list ref]; Haiyang Zhang [off-list ref];
Michael S.
quoted
Tsirkin [off-list ref]; Shrikrishna Khare [off-list ref];
VMware,
quoted
Inc. [off-list ref]; Wei Liu [off-list ref]; Paul
Durrant [off-list ref]; David Kershner
[off-list ref]
Subject: [PATCH net-next v2 6/9] net: use core MTU range checking in
virt drivers
hyperv_net:
- set min/max_mtu, per Haiyang, after rndis_filter_device_add
virtio_net:
- set min/max_mtu
- remove virtnet_change_mtu
vmxnet3:
- set min/max_mtu
xen-netback:
- min_mtu = 0, max_mtu = 65517
xen-netfront:
- min_mtu = 0, max_mtu = 65535
unisys/visor:
- clean up defines a little to not clash with network core or add
redundat definitions
CC: <redacted>
CC: <redacted>
CC: "K. Y. Srinivasan" <redacted>
CC: Haiyang Zhang <haiyangz@microsoft.com>
CC: "Michael S. Tsirkin" <mst@redhat.com>
CC: Shrikrishna Khare <redacted>
CC: "VMware, Inc." <redacted>
CC: Wei Liu <redacted>
CC: Paul Durrant <redacted>
CC: David Kershner <redacted>
Signed-off-by: Jarod Wilson <redacted>
---
The hv_netvsc changes look fine. Thanks.
Reviewed-by: Haiyang Zhang <haiyangz@microsoft.com>
The visornic changes look good.
Reviewed-by: David Kershner <redacted>