From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: confusing comment, explanation of @IFF_RUNNING in if.h Date: Sun, 26 Aug 2018 13:51:44 -0700 Message-ID: <20180826135144.11fd9a5f@xeon-e3> References: <20180826192001.GC7359@lunn.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Andrew Lunn , Linux kernel netdev mailing list To: "Robert P. J. Day" Return-path: Received: from mail-pl1-f176.google.com ([209.85.214.176]:44708 "EHLO mail-pl1-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726714AbeH0Af0 (ORCPT ); Sun, 26 Aug 2018 20:35:26 -0400 Received: by mail-pl1-f176.google.com with SMTP id ba4-v6so3207828plb.11 for ; Sun, 26 Aug 2018 13:51:47 -0700 (PDT) In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Sun, 26 Aug 2018 15:20:24 -0400 (EDT) "Robert P. J. Day" wrote: > On Sun, 26 Aug 2018, Andrew Lunn wrote: > > > > 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. > > rday > So you expect FOSS developers to help you with proprietary licensed driver. Good Luck with that.