netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Richard Knutsson <ricknu-0@student.ltu.se>
Cc: linville@tuxdriver.com, netdev@vger.kernel.org
Subject: Re: [RFC] airo.c: Description and function is not the same
Date: Tue, 23 Jan 2007 10:11:34 -0500	[thread overview]
Message-ID: <1169565094.2777.9.camel@localhost.localdomain> (raw)
In-Reply-To: <45B35616.6040103@student.ltu.se>

On Sun, 2007-01-21 at 13:01 +0100, Richard Knutsson wrote:
> Hello
> 
> In the tour of converting local definitions of boolean-type/values, I 
> ran into airo.c's description of ex decapsulate():
> 
>  *      Returns: BOOLEAN - TRUE if packet should be dropped otherwise FALSE
> 
> but returns SUCCESS (defined as 0) and ERROR (defined as -1).
> 
> Also, shouldn't those functions be converted to return 'bool' when the 
> description say so (happy to do it).

Does anyone use the Cisco MIC code anymore? I guess we can't just rip it
out...  It was a proprietary Cisco extension back before WPA.

In any case, the comment should be changed to reflect the current return
values of the function, and SUCCESS and ERROR in decapsulate() should be
changed to 0 and -1 respectively; defining stuff like success/error just
makes things ugly, and 0 and -1 are well-enough-known that there should
be no question what they mean.

Essentially, the code is using 0 and -1 as booleans anyway.  I say get
rid of SUCCESS & ERROR and just use 0 and -1, then change the comment.

dan

> Richard Knutsson
> 
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


      reply	other threads:[~2007-01-23 15:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-21 12:01 [RFC] airo.c: Description and function is not the same Richard Knutsson
2007-01-23 15:11 ` Dan Williams [this message]

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=1169565094.2777.9.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.org \
    --cc=ricknu-0@student.ltu.se \
    /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).