From mboxrd@z Thu Jan  1 00:00:00 1970
From: Julian Wiedmann <jwi@linux.ibm.com>
Subject: Re: for newbies, it would be useful to document values of
 netdev_state_t
Date: Wed, 8 Aug 2018 10:45:07 +0200
Message-ID: <7cdb2440-6c91-9336-9147-e69b700e93f7@linux.ibm.com>
References: <alpine.LFD.2.21.1808041128280.23447@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
        Linux kernel ntedev mailing list <netdev@vger.kernel.org>
Return-path: <netdev-owner@vger.kernel.org>
Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:37790 "EHLO
        mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK)
        by vger.kernel.org with ESMTP id S1726979AbeHHLD4 (ORCPT
        <rfc822;netdev@vger.kernel.org>); Wed, 8 Aug 2018 07:03:56 -0400
Received: from pps.filterd (m0098409.ppops.net [127.0.0.1])
        by mx0a-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w788dPVY093479
        for <netdev@vger.kernel.org>; Wed, 8 Aug 2018 04:45:14 -0400
Received: from e06smtp04.uk.ibm.com (e06smtp04.uk.ibm.com [195.75.94.100])
        by mx0a-001b2d01.pphosted.com with ESMTP id 2kqw418cbn-1
        (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT)
        for <netdev@vger.kernel.org>; Wed, 08 Aug 2018 04:45:14 -0400
Received: from localhost
        by e06smtp04.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted
        for <netdev@vger.kernel.org> from <jwi@linux.ibm.com>;
        Wed, 8 Aug 2018 09:45:12 +0100
In-Reply-To: <alpine.LFD.2.21.1808041128280.23447@localhost.localdomain>
Content-Language: en-US
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

On 08/04/2018 05:30 PM, 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.
> 
> rday
> 

It is far from perfect, but Documentation/networking/operstates.txt
might get you started.