[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150924222654.GG20825@lunn.ch>
Date: Fri, 25 Sep 2015 00:26:54 +0200
From: Andrew Lunn <andrew@...n.ch>
To: David Miller <davem@...emloft.net>
Cc: linux@....linux.org.uk, f.fainelli@...il.com,
thomas.petazzoni@...e-electrons.com, devicetree@...r.kernel.org,
sgoutham@...ium.com, rric@...nel.org, frowand.list@...il.com,
linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
robh+dt@...nel.org, michal.simek@...inx.com,
netdev@...r.kernel.org, soren.brinkmann@...inx.com,
isubramanian@....com, grant.likely@...aro.org, leoli@...escale.com,
kchudgar@....com, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v3 0/9] Phy, mdiobus, and netdev struct device fixes
On Thu, Sep 24, 2015 at 03:15:54PM -0700, David Miller wrote:
> From: Andrew Lunn <andrew@...n.ch>
> Date: Thu, 24 Sep 2015 23:57:31 +0200
>
> > 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>
>
> So, is this a regression?
Sorry, worded that badly. Since DSA is still active, it should not be
possible to unload the FEC driver. DSA should have a reference to it,
and mdio-mux also should have a reference to the mdio bus of the FEC
driver.
As Russell requested, i will re-test without his patches, just to make
sure.
Andrew
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists