diff options
| author | Jarod Wilson <jarod@redhat.com> | 2016-10-07 22:04:34 -0400 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2016-10-13 09:36:57 -0400 |
| commit | a52ad514fdf3b8a57ca4322c92d2d8d5c6182485 (patch) | |
| tree | d5c763c23ce3faa611fa00b386f9a095ad364315 /arch | |
| parent | 61e84623ace35ce48975e8f90bbbac7557c43d61 (diff) | |
| download | linux-a52ad514fdf3b8a57ca4322c92d2d8d5c6182485.tar.gz linux-a52ad514fdf3b8a57ca4322c92d2d8d5c6182485.tar.bz2 linux-a52ad514fdf3b8a57ca4322c92d2d8d5c6182485.zip | |
net: deprecate eth_change_mtu, remove usage
With centralized MTU checking, there's nothing productive done by
eth_change_mtu that isn't already done in dev_set_mtu, so mark it as
deprecated and remove all usage of it in the kernel. All callers have been
audited for calls to alloc_etherdev* or ether_setup directly, which means
they all have a valid dev->min_mtu and dev->max_mtu. Now eth_change_mtu
prints out a netdev_warn about being deprecated, for the benefit of
out-of-tree drivers that might be utilizing it.
Of note, dvb_net.c actually had dev->mtu = 4096, while using
eth_change_mtu, meaning that if you ever tried changing it's mtu, you
couldn't set it above 1500 anymore. It's now getting dev->max_mtu also set
to 4096 to remedy that.
v2: fix up lantiq_etop, missed breakage due to drive not compiling on x86
CC: netdev@vger.kernel.org
Signed-off-by: Jarod Wilson <jarod@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'arch')
| -rw-r--r-- | arch/m68k/emu/nfeth.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/arch/m68k/emu/nfeth.c b/arch/m68k/emu/nfeth.c index a0985fd088d1..fc4be028c418 100644 --- a/arch/m68k/emu/nfeth.c +++ b/arch/m68k/emu/nfeth.c @@ -184,7 +184,6 @@ static const struct net_device_ops nfeth_netdev_ops = { .ndo_start_xmit = nfeth_xmit, .ndo_tx_timeout = nfeth_tx_timeout, .ndo_validate_addr = eth_validate_addr, - .ndo_change_mtu = eth_change_mtu, .ndo_set_mac_address = eth_mac_addr, }; |