From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Linux kernel netdev mailing list <netdev@vger.kernel.org>
Subject: Re: followup: what's responsible for setting netdev->operstate to IF_OPER_DOWN?
Date: Sun, 26 Aug 2018 15:26:11 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.21.1808261525001.9594@localhost.localdomain> (raw)
In-Reply-To: <20180826192445.GD7359@lunn.ch>
On Sun, 26 Aug 2018, Andrew Lunn wrote:
> 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.
i'm not sure i'm even allowed to talk about that given the NDA --
i'll just muddle through following the code until i figure out what is
failing to notify userspace. le *sigh*.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca/dokuwiki
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2018-08-26 23:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-26 15:14 followup: what's responsible for setting netdev->operstate to IF_OPER_DOWN? Robert P. J. Day
2018-08-26 19:24 ` Andrew Lunn
2018-08-26 19:26 ` Robert P. J. Day [this message]
2018-08-26 20:50 ` Stephen Hemminger
2018-08-27 6:22 ` Robert P. J. Day
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.21.1808261525001.9594@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=andrew@lunn.ch \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).