Netdev List
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
	Linux kernel ntedev mailing list <netdev@vger.kernel.org>
Subject: Re: for newbies, it would be useful to document values of netdev_state_t
Date: Sat, 4 Aug 2018 11:10:34 -0700	[thread overview]
Message-ID: <bc33b6c0-6dbc-9d63-e798-b999b7601c3b@gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.21.1808041128280.23447@localhost.localdomain>



On 08/04/2018 08:30 AM, Robert P. J. Day wrote:
> 
>   i'm sure this is second nature for the experts here, but in
> netdevice.h:
> 
> /* These flag bits are private to the generic network queueing
>  * layer; they may not be explicitly referenced by any other
>  * code.
>  */
> 
> enum netdev_state_t {
>         __LINK_STATE_START,
>         __LINK_STATE_PRESENT,
>         __LINK_STATE_NOCARRIER,
>         __LINK_STATE_LINKWATCH_PENDING,
>         __LINK_STATE_DORMANT,
> };
> 
> it would be handy to have a short explanation of what each state
> represents, perhaps what combinations are possible and how one moves
> from one state to another.

This has been like that for some time, and with the exception of the
problem you reported in your email before that one, people generally
don't muck with that enum, or the state machine consuming it. There
might be other places that could deserve better documentation ;)
-- 
Florian

  reply	other threads:[~2018-08-04 20:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-04 15:30 for newbies, it would be useful to document values of netdev_state_t Robert P. J. Day
2018-08-04 18:10 ` Florian Fainelli [this message]
2018-08-08  8:45 ` Julian Wiedmann

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=bc33b6c0-6dbc-9d63-e798-b999b7601c3b@gmail.com \
    --to=f.fainelli@gmail.com \
    --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