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 09:25:32 -0700 [thread overview]
Message-ID: <1213028732.5974.13.camel@brick> (raw)
In-Reply-To: <1212997025.698.51.camel@johannes.berg>
On Mon, 2008-06-09 at 09:37 +0200, Johannes Berg wrote:
> > +static inline u8 *ieee80211_get_qos_ctl(struct ieee80211_hdr *hdr,
>
> I think this is wrong, the header len will probably at some point
> include more things like HT headers where present or similar, so
> subtracting 2 from the header len is going to be wrong as soon as that
> happens because the QoS control will stay first. I think this should do
> the relevant calculation itself, ie. check for A4.
OK.
>
> > +static inline int ieee80211_has_protected(__le16 fc)
>
> > +static inline int ieee80211_has_morefrags(__le16 fc)
>
> > +static inline int ieee80211_has_tods(__le16 fc)
>
> > +static inline int ieee80211_has_fromds(__le16 fc)
>
> > +static inline int ieee80211_has_a4(__le16 fc)
>
> > +static inline int ieee80211_is_mgmt(__le16 fc)
>
> > +static inline int ieee80211_is_ctl(__le16 fc)
>
> > +static inline int ieee80211_is_data(__le16 fc)
>
> > +static inline int ieee80211_data_has_qos(__le16 fc)
>
> Can you add kernel-doc comments for these?
OK.
Harvey
next prev parent reply other threads:[~2008-06-09 16:25 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 [this message]
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
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=1213028732.5974.13.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).