From: Ingo Oeser <netdev@axxeo.de>
To: Ralf Baechle DL5RB <ralf@linux-mips.org>
Cc: "David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, linux-hams@vger.kernel.org
Subject: Re: [PATCH 5/12] Add descriptions to constants
Date: Mon, 12 Sep 2005 18:41:53 +0200 [thread overview]
Message-ID: <200509121841.53666.netdev@axxeo.de> (raw)
In-Reply-To: <20050911221904.GA9301@linux-mips.org>
Hi Ralf,
Ralf Baechle DL5RB wrote:
> Comment the names used for the AX.25 state machine.
What about making it even more useful by aliasing the enum elements?
> Signed-off-by: Ralf Baechle DL5RB <ralf@linux-mips.org>
>
> include/net/ax25.h | 10 +++++-----
> 1 files changed, 5 insertions(+), 5 deletions(-)
>
> Index: linux-cvs/include/net/ax25.h
> ===================================================================
> --- linux-cvs.orig/include/net/ax25.h
> +++ linux-cvs/include/net/ax25.h
> @@ -97,11 +97,11 @@
> /* Define Link State constants. */
>
> enum {
> - AX25_STATE_0,
> - AX25_STATE_1,
> - AX25_STATE_2,
> - AX25_STATE_3,
> - AX25_STATE_4
> + AX25_STATE_0, /* Listening */
+ AX25_STATE_LISTENING = AX25_STATE_0,
> + AX25_STATE_1, /* SABM sent */
+ AX25_STATE_SABM_SENT = AX25_STATE_1,
> + AX25_STATE_2, /* DISC sent */
+ AX25_STATE_DISC_SENT = AX25_STATE_2,
> + AX25_STATE_3, /* Established */
+ AX25_STATE_ESTABLISHED = AX25_STATE_3,
> + AX25_STATE_4 /* Recovery */
+ AX25_STATE_RECOVERY = AX25_STATE_4,
> };
That would not break backward compatibility and now the state machine can be
self explanatory :-)
Regards
Ingo Oeser
next prev parent reply other threads:[~2005-09-12 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-11 22:19 [PATCH 5/12] Add descriptions to constants Ralf Baechle DL5RB
2005-09-12 16:41 ` Ingo Oeser [this message]
2005-09-12 16:50 ` Ralf Baechle
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=200509121841.53666.netdev@axxeo.de \
--to=netdev@axxeo.de \
--cc=davem@davemloft.net \
--cc=linux-hams@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.org \
/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).