This is a note to let you know that I've just added the patch titled
net: dsa: Bring back device detaching in dsa_slave_suspend()
to the 4.9-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
net-dsa-bring-back-device-detaching-in-dsa_slave_suspend.patch
and it can be found in the queue-4.9 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
>From foo@baz Wed Feb 1 08:50:24 CET 2017
From: Florian Fainelli <f.fainelli@xxxxxxxxx>
Date: Wed, 25 Jan 2017 09:10:41 -0800
Subject: net: dsa: Bring back device detaching in dsa_slave_suspend()
From: Florian Fainelli <f.fainelli@xxxxxxxxx>
[ Upstream commit f154be241d22298d2b63c9b613f619fa1086ea75 ]
Commit 448b4482c671 ("net: dsa: Add lockdep class to tx queues to avoid
lockdep splat") removed the netif_device_detach() call done in
dsa_slave_suspend() which is necessary, and paired with a corresponding
netif_device_attach(), bring it back.
Fixes: 448b4482c671 ("net: dsa: Add lockdep class to tx queues to avoid lockdep splat")
Signed-off-by: Florian Fainelli <f.fainelli@xxxxxxxxx>
Reviewed-by: Andrew Lunn <andrew@xxxxxxx>
Signed-off-by: David S. Miller <davem@xxxxxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
net/dsa/slave.c | 2 ++
1 file changed, 2 insertions(+)
--- a/net/dsa/slave.c
+++ b/net/dsa/slave.c
@@ -1201,6 +1201,8 @@ int dsa_slave_suspend(struct net_device
{
struct dsa_slave_priv *p = netdev_priv(slave_dev);
+ netif_device_detach(slave_dev);
+
if (p->phy) {
phy_stop(p->phy);
p->old_pause = -1;
Patches currently in stable-queue which might be from f.fainelli@xxxxxxxxx are
queue-4.9/net-systemport-decouple-flow-control-from-__bcm_sysport_tx_reclaim.patch
queue-4.9/net-dsa-bring-back-device-detaching-in-dsa_slave_suspend.patch
queue-4.9/net-phy-bcm63xx-utilize-correct-config_intr-function.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html