From: Stephen Hemminger <stephen@networkplumber.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Andrew Lunn <andrew@lunn.ch>,
Linux kernel netdev mailing list <netdev@vger.kernel.org>
Subject: Re: confusing comment, explanation of @IFF_RUNNING in if.h
Date: Sun, 26 Aug 2018 13:51:44 -0700 [thread overview]
Message-ID: <20180826135144.11fd9a5f@xeon-e3> (raw)
In-Reply-To: <alpine.LFD.2.21.1808261518250.8901@localhost.localdomain>
On Sun, 26 Aug 2018 15:20:24 -0400 (EDT)
"Robert P. J. Day" <rpjday@crashcourse.ca> 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.
next prev parent reply other threads:[~2018-08-27 0:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-26 8:13 confusing comment, explanation of @IFF_RUNNING in if.h Robert P. J. Day
2018-08-26 19:20 ` Andrew Lunn
2018-08-26 19:20 ` Robert P. J. Day
2018-08-26 19:28 ` Andrew Lunn
2018-08-26 19:30 ` Robert P. J. Day
2018-08-26 20:51 ` Stephen Hemminger [this message]
2018-08-27 6:20 ` Robert P. J. Day
2018-08-27 7:11 ` Oliver Hartkopp
2018-08-27 8:04 ` 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=20180826135144.11fd9a5f@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=andrew@lunn.ch \
--cc=netdev@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
/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).