From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: Roberto Riggio <roberto.riggio-2TmCWn7/4sHOQU1ULcgDhA@public.gmane.org>
Cc: "radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org"
<radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org>
Subject: Re: Handling RADIOTAP_EXT
Date: Wed, 07 Mar 2012 09:29:25 +0100 [thread overview]
Message-ID: <1331108965.3519.9.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4F571A36.8020405-2TmCWn7/4sHOQU1ULcgDhA@public.gmane.org>
On Wed, 2012-03-07 at 09:20 +0100, Roberto Riggio wrote:
> On 03/07/2012 09:10 AM, Johannes Berg wrote:
> > Can you elaborate what you mean? Do you want to keep something while
> > using the library?
>
> Let's assume that I'm the the following situation:
>
> ---
> RATE (1) 54 Mbps
> COUNT (1) 3
> ---
> RATE (2) 18 Mbps
> COUNT (2) 3
> ---
> RATE (3) 6 Mbps
> COUNT (3) 3
> ---
>
> When I'm iterating over the header I could keep track of the namespace
> by incrementing an index after I have found the RETRIES field. This will
> work because the RETRIES field is always after the RATE field so my
> index is consistent.
>
> On the other hand, if in the header MCS and RETRIES the approach above
> will not work, since the MCS field is after the RETRIES field.
>
> So I was wondering if there is a way, while iterating over an header, to
> known how many time the RADIOTAP_NAMESPACE (or the EXT) field has been
> found.
Ah, no, not with the library as it is today. I suppose we could add a
flag "inform me of namespace boundaries" or something like that.
johannes
prev parent reply other threads:[~2012-03-07 8:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 21:54 Handling RADIOTAP_EXT Roberto Riggio
[not found] ` <4F56879E.9030907-2TmCWn7/4sHOQU1ULcgDhA@public.gmane.org>
2012-03-07 8:10 ` Johannes Berg
[not found] ` <1331107859.3519.4.camel-8upI4CBIZJIJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2012-03-07 8:20 ` Roberto Riggio
[not found] ` <4F571A36.8020405-2TmCWn7/4sHOQU1ULcgDhA@public.gmane.org>
2012-03-07 8:29 ` Johannes Berg [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=1331108965.3519.9.camel@jlt3.sipsolutions.net \
--to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
--cc=radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org \
--cc=roberto.riggio-2TmCWn7/4sHOQU1ULcgDhA@public.gmane.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).