[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200421123110.13733-3-olteanv@gmail.com>
Date: Tue, 21 Apr 2020 15:31:10 +0300
From: Vladimir Oltean <olteanv@...il.com>
To: andrew@...n.ch, f.fainelli@...il.com, vivien.didelot@...il.com,
davem@...emloft.net, o.rempel@...gutronix.de
Cc: netdev@...r.kernel.org
Subject: [PATCH net 2/2] net: dsa: don't fail to probe if we couldn't set the MTU
From: Vladimir Oltean <vladimir.oltean@....com>
There is no reason to fail the probing of the switch if the MTU couldn't
be configured correctly (either the switch port itself, or the host
port) for whatever reason. MTU-sized traffic probably won't work, sure,
but we can still probably limp on and support some form of communication
anyway, which the users would probably appreciate more.
Fixes: bfcb813203e6 ("net: dsa: configure the MTU for switch ports")
Reported-by: Oleksij Rempel <o.rempel@...gutronix.de>
Signed-off-by: Vladimir Oltean <vladimir.oltean@....com>
---
net/dsa/slave.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/net/dsa/slave.c b/net/dsa/slave.c
index 3776a6f6d312..34071d9bab3f 100644
--- a/net/dsa/slave.c
+++ b/net/dsa/slave.c
@@ -1773,11 +1773,9 @@ int dsa_slave_create(struct dsa_port *port)
rtnl_lock();
ret = dsa_slave_change_mtu(slave_dev, mtu);
rtnl_unlock();
- if (ret && ret != -EOPNOTSUPP) {
+ if (ret)
dev_err(ds->dev, "error %d setting MTU on port %d\n",
ret, port->index);
- goto out_free;
- }
netif_carrier_off(slave_dev);
--
2.17.1
Powered by blists - more mailing lists