On 18/10/2016 15:24, Andrew Lunn wrote:
>> Hi Andrew
>> i am testing on v4.4 which did not have a phy_disconnect() call. this
>> seems to have been fixed by cda5c15b so please ignore this patch
> Hi John
> All patches must be against net-next, or net if it is a fix. Anything
> else is wrong....
i know. i was testing on v4.4 and then rebased the patch against
net-next without noticing that a similar patch had already been merged.
regardless, using the latest net-next tree, the oops is gone without
adding any patches.