[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150924215731.GE20825@lunn.ch>
Date: Thu, 24 Sep 2015 23:57:31 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Russell King - ARM Linux <linux@....linux.org.uk>
Cc: Florian Fainelli <f.fainelli@...il.com>,
David Miller <davem@...emloft.net>,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
devicetree@...r.kernel.org, Sunil Goutham <sgoutham@...ium.com>,
Robert Richter <rric@...nel.org>,
Frank Rowand <frowand.list@...il.com>,
linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
Rob Herring <robh+dt@...nel.org>,
Michal Simek <michal.simek@...inx.com>, netdev@...r.kernel.org,
Soren Brinkmann <soren.brinkmann@...inx.com>,
Iyappan Subramanian <isubramanian@....com>,
Grant Likely <grant.likely@...aro.org>,
Li Yang <leoli@...escale.com>,
Keyur Chudgar <kchudgar@....com>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v3 0/9] Phy, mdiobus, and netdev struct device fixes
...
> While looking at the DSA code, I noticed we have a
> of_find_net_device_by_node(), and it looks like users of that are
> similarly buggy - it looks like net/dsa/dsa.c is the only user. Fix
> that too.
...
> The mdiobus code also suffered from the same kind of leak, but thankfully
> this only happened in one place - the mdio-mux code.
Hi Russell
I tested both of these with my board. It is a Freescale Vybrid, using
the FEC ethernet driver, and i have three switches attached, using
mdio-mux to give three mdio busses.
No obvious regressions, my board boots, the switches are all present
and correct. I built the FEC driver as a module, and it won't unload:
kernel:unregister_netdevice: waiting for eth1 to become free. Usage count = 1
unregister_netdevice: waiting for eth1 to become free. Usage count = 1
i assume because DSA holds a reference. I've not tried a fully module
build, DSA has issues with that.
Tested-by: Andrew Lunn <andrew@...n.ch>
Thanks
Andrew
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists