linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: "C. McPherson" <ccmcphe@verizon.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>, radiotap@radiotap.org
Subject: Re: Vendor Namespace Question
Date: Thu, 06 Nov 2014 23:31:10 +0100	[thread overview]
Message-ID: <1415313070.17015.19.camel@sipsolutions.net> (raw)
In-Reply-To: <5459349F.9020903@verizon.net>

On Tue, 2014-11-04 at 15:18 -0500, C. McPherson wrote:
> Thanks so much for the info Johannes. I did notice that rx_status was 
> getting full.  I'll go ahead and put it in skb->data, that's a good idea.

I just sent a patch to restore vendor radiotap stuff in mac80211.

Works for me, and I might actually have a use case for it, but please
tell me if you have issues with it.

johannes


  reply	other threads:[~2014-11-06 22:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04 18:37 Vendor Namespace Question C. McPherson
2014-11-04 19:47 ` Johannes Berg
2014-11-04 20:18   ` C. McPherson
2014-11-06 22:31     ` Johannes Berg [this message]
2014-11-12 20:55       ` C. McPherson

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=1415313070.17015.19.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=ccmcphe@verizon.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=radiotap@radiotap.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).