linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Harvey Harrison <harvey.harrison@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	John Linville <linville@tuxdriver.com>
Subject: Re: [RFC-PATCH] mac80211: add helpers for frame control tests
Date: Fri, 16 May 2008 16:48:07 -0700	[thread overview]
Message-ID: <1210981687.5915.67.camel@brick> (raw)
In-Reply-To: <1210975426.6381.70.camel@johannes.berg>

On Sat, 2008-05-17 at 00:03 +0200, Johannes Berg wrote:
> On Fri, 2008-05-16 at 14:57 -0700, Harvey Harrison wrote:
> > On Fri, 2008-05-16 at 23:12 +0200, Johannes Berg wrote:
> > > 
> > > Right. Still, I think it should be named with _is_ in there.
> > 
> > Yes, I agree with you, that's what I meant to write.
> 
> Actually, maybe it should be "has" and not "is" since it's being passed
> a frame that can *have* a given frame type, and is a frame of a given
> type. Dunno.

I think _is_ works best, I'll send out a few trial patches, but this
seems to make sense in the places its used.

> 
> > Ahhh, I see what you are getting at now, how about ieee80211_stype_mask?
> > 
> > That makes the & a little clearer and has better semantic meaning.
> > 
> > The other option is still to call it stype_mask, but change it to
> > return a __le16....so tests against != 0 still work and really
> > is just a wrapper around the byteswap of the constant and the &.
> 
> Hmm. I'm not sure, how is all this really used? It seems you want
> 
> ieee80211_has_qos_stype(hdr)
> and
> 
> ieee80211_has_stype(hdr, stype)
> 
> instead, no?

Just the latter I think.  But I'll do a few patches to see how it looks
first.  If there end up being a few common ones (like qos) a few
short-hand versions might be appropriate, I'll see how it goes.

Harvey


  reply	other threads:[~2008-05-16 23:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-16 19:29 [RFC-PATCH] mac80211: add helpers for frame control tests Harvey Harrison
2008-05-16 19:38 ` Harvey Harrison
2008-05-16 20:31   ` Johannes Berg
2008-05-16 20:40     ` Johannes Berg
2008-05-16 21:04     ` Harvey Harrison
2008-05-16 21:12       ` Johannes Berg
2008-05-16 21:57         ` Harvey Harrison
2008-05-16 22:03           ` Johannes Berg
2008-05-16 23:48             ` Harvey Harrison [this message]
2008-05-17  9:12               ` Johannes Berg
2008-05-16 20:42   ` Michael Buesch

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=1210981687.5915.67.camel@brick \
    --to=harvey.harrison@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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).