From: Harvey Harrison <harvey.harrison@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/7] mac80211: add helpers for frame control testing
Date: Mon, 09 Jun 2008 10:54:19 -0700 [thread overview]
Message-ID: <1213034059.5974.33.camel@brick> (raw)
In-Reply-To: <1213033579.22220.8.camel@johannes.berg>
On Mon, 2008-06-09 at 19:46 +0200, Johannes Berg wrote:
> On Mon, 2008-06-09 at 10:43 -0700, Harvey Harrison wrote:
> > On Mon, 2008-06-09 at 19:21 +0200, Johannes Berg wrote:
> > > On Mon, 2008-06-09 at 09:31 -0700, Harvey Harrison wrote:
> > > >
> > > > As this helper only checks for the one bit being set, I chose _has_.
> > >
> > > Hmm. As far as I can tell, it checks that the frame is a QoS controlled
> > > data frame. Hence, it explicitly checks that it _is_ a data frame and
> > > _has_ the QoS bit, but in 802.11 lingo I think that means it _is_ a
> > > "data+qos" frame.
> > >
> >
> > Well, it's not a big deal...what name do you want and I'll change it.
>
> I'd prefer _is_qos_data because _data_has_qos makes me think I have to
> ensure that the frame is a data frame before passing it in, i.e. it will
> return undefined results for a management/control frame.
Well, the way the other functions of the same type:
ieee80211_ctl_is_ack
ieee80211_mgmt_is_beacon
check not only that the ftype is exactly ctl/mgmt and that it is of
stype ack/beacon. I chose ieee80211_data_has_qos because it checks
the ftype _is_ data _and_ that it _has_ qos included. I think my
naming is more consistent with this.
Do you still think it should be changed?
Cheers,
Harvey
next prev parent reply other threads:[~2008-06-09 17:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 17:51 [PATCH 1/7] mac80211: add helpers for frame control testing Harvey Harrison
2008-06-09 7:37 ` Johannes Berg
2008-06-09 16:25 ` Harvey Harrison
2008-06-09 7:41 ` Johannes Berg
2008-06-09 16:31 ` Harvey Harrison
2008-06-09 17:21 ` Johannes Berg
2008-06-09 17:43 ` Harvey Harrison
2008-06-09 17:46 ` Johannes Berg
2008-06-09 17:54 ` Harvey Harrison [this message]
2008-06-09 18:02 ` Johannes Berg
2008-06-09 18:22 ` Harvey Harrison
2008-06-09 18:27 ` Johannes Berg
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=1213034059.5974.33.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.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).