Re: confusing comment, explanation of @IFF_RUNNING in if.h

On Sun, Aug 26, 2018 at 03:20:24PM -0400, Robert P. J. Day wrote:

On Sun, 26 Aug 2018, Andrew Lunn wrote:

quoted

quoted

  i ask since, in my testing, when the interface should have been
up, the attribute file "operstate" for that interface showed
"unknown", and i wondered how worried i should be about that.

Hi Robert

You should probably post the driver for review. A well written
driver should not even need to care about any of this. phylib and
the netdev driver code does all the work. It only gets interesting
when you don't have a PHY, e.g. a stacked device, like bonding, or a
virtual device like tun/tap.

  i wish, but i'm on contract, and proprietary, and NDA and all that.
so i am reduced to crawling through the code, trying to figure out
what is misconfigured that is causing all this grief.

I would say proprietary and NDA is causing you all this grief.

There is also the point that if you are not going to contribute the
code to mainline, why should we help you?

The code is GPL after all, so you can post it.

  Andrew