All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Marcelo Tosatti <marcelo@kvack.org>
Cc: David Young <dyoung@pobox.com>,
	linux-wireless@vger.kernel.org,
	Scott Raynel <scottraynel@gmail.com>,
	radiotap@mail.ojctech.com
Subject: Re: [Radiotap] Re: RFC: radiotap discrepancy in Linux vs OpenBSD
Date: Wed, 28 Mar 2007 16:33:32 -0400	[thread overview]
Message-ID: <1175114012.9299.4.camel@dv> (raw)
In-Reply-To: <20070328180413.GC17793@dmt>

On Wed, 2007-03-28 at 15:04 -0300, Marcelo Tosatti wrote:
> On Mon, Mar 26, 2007 at 06:45:49PM -0400, Pavel Roskin wrote:
> > On Sun, 2007-03-25 at 22:37 -0500, David Young wrote:
> > 
> > > > One is found in the current wireless-2.6.git:
> > > > 
> > > >         IEEE80211_RADIOTAP_RX_FLAGS = 14,
> > > >         IEEE80211_RADIOTAP_TX_FLAGS = 15,
> > > >         IEEE80211_RADIOTAP_RTS_RETRIES = 16,
> > > >         IEEE80211_RADIOTAP_DATA_RETRIES = 17,
> > > 
> > > These fields are slated to become part of the standard, I just haven't got
> > > around to updating the manual page, yet.  I have time to do that tonight.
> > 
> > OK.  I was wrong to assume that non-standard fields were introduced on
> > the Linux side.
> 
> I mentioned those in the past to David Young, but I forgot to resend
> them to the radiotap list. 

Then we need to remove IEEE80211_RADIOTAP_FCS from Linux
ieee80211_radiotap.h.  It's only present in a comment, but it's a
comment that can be harmful.  I could submit a patch, but it would
conflict with a patch that does sparse annotation.

OK, I'll submit both.

-- 
Regards,
Pavel Roskin


  parent reply	other threads:[~2007-03-28 20:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-26  3:24 RFC: radiotap discrepancy in Linux vs OpenBSD Pavel Roskin
2007-03-26  3:37 ` David Young
     [not found]   ` <20070326033729.GG31621-eZ+MEZF6i8Dc+919tysfdA@public.gmane.org>
2007-03-26 22:45     ` Pavel Roskin
2007-03-26 22:45   ` Pavel Roskin
2007-03-28 18:04     ` [Radiotap] " Marcelo Tosatti
2007-03-28 20:33       ` Pavel Roskin
2007-03-28 20:33       ` Pavel Roskin [this message]
2007-03-28 18:04     ` Marcelo Tosatti
2007-03-26  3:38 ` David Young
2007-03-26 15:41   ` Luis R. Rodriguez
2007-03-26 16:59     ` David Young
     [not found]     ` <43e72e890703260841v56047559y90b7c25c9c458564-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-03-26 16:59       ` David Young
     [not found]   ` <20070326033839.GA24097-eZ+MEZF6i8Dc+919tysfdA@public.gmane.org>
2007-03-26 15:41     ` Luis R. Rodriguez
     [not found] ` <20070325232416.64xwkc0kw04oosg0-2RFepEojUI3Rd1RZctBqVdHuzzzSOjJt@public.gmane.org>
2007-03-26  3:38   ` David Young

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=1175114012.9299.4.camel@dv \
    --to=proski@gnu.org \
    --cc=dyoung@pobox.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marcelo@kvack.org \
    --cc=radiotap@mail.ojctech.com \
    --cc=scottraynel@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.