From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Lunn <andrew@lunn.ch>
Subject: Re: followup: what's responsible for setting netdev->operstate to
 IF_OPER_DOWN?
Date: Sun, 26 Aug 2018 21:24:45 +0200
Message-ID: <20180826192445.GD7359@lunn.ch>
References: <alpine.LFD.2.21.1808261102450.13415@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Linux kernel netdev mailing list <netdev@vger.kernel.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Return-path: <netdev-owner@vger.kernel.org>
Received: from vps0.lunn.ch ([185.16.172.187]:43402 "EHLO vps0.lunn.ch"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1726625AbeHZXIM (ORCPT <rfc822;netdev@vger.kernel.org>);
        Sun, 26 Aug 2018 19:08:12 -0400
Content-Disposition: inline
In-Reply-To: <alpine.LFD.2.21.1808261102450.13415@localhost.localdomain>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

On Sun, Aug 26, 2018 at 11:14:33AM -0400, Robert P. J. Day wrote:
> 
>   apologies for the constant pleas for assistance, but i think i'm
> zeroing in on the problem that started all this. recap: custom
> FPGA-based linux box with multiple ports, where the current symptom is
> that there is no userspace notification when someone simply unplugs
> one of the ports ("ifconfig" shows that interface still RUNNING).

What are you using for a PHY? Are you using phylib or phylink?  I
strongly suggest you do, and then you don't need to care about any of
this.

	Andrew