From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Lunn <andrew@lunn.ch>
Subject: Re: confusing comment, explanation of @IFF_RUNNING in if.h
Date: Sun, 26 Aug 2018 21:20:01 +0200
Message-ID: <20180826192001.GC7359@lunn.ch>
References: <alpine.LFD.2.21.1808260410530.31293@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]:43392 "EHLO vps0.lunn.ch"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1726694AbeHZXD2 (ORCPT <rfc822;netdev@vger.kernel.org>);
        Sun, 26 Aug 2018 19:03:28 -0400
Content-Disposition: inline
In-Reply-To: <alpine.LFD.2.21.1808260410530.31293@localhost.localdomain>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

>   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.

     Andrew