All of lore.kernel.org
 help / color / mirror / Atom feed
From: "C. McPherson" <ccmcphe@verizon.net>
To: linux-wireless <linux-wireless@vger.kernel.org>, radiotap@radiotap.org
Subject: Vendor Namespace Question
Date: Tue, 04 Nov 2014 13:37:45 -0500	[thread overview]
Message-ID: <54591CF9.7030106@verizon.net> (raw)

Hello all:
I was just trying to use the latest stable backports-3.18-rc1-1 and I 
noticed that there is no longer structure members in the 
ieee80211_rx_status structure for Vendor namespace information?  In my 
backports 3.14 version I used them to add some register information to 
the radiotap header in the lab. How does one use the vendor name space 
without those structure members?

Thanks for you assistance
Clyde



WARNING: multiple messages have this Message-ID (diff)
From: "C. McPherson" <ccmcphe-H+0wwilmMs3R7s880joybQ@public.gmane.org>
To: linux-wireless
	<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org
Subject: Vendor Namespace Question
Date: Tue, 04 Nov 2014 13:37:45 -0500	[thread overview]
Message-ID: <54591CF9.7030106@verizon.net> (raw)

Hello all:
I was just trying to use the latest stable backports-3.18-rc1-1 and I 
noticed that there is no longer structure members in the 
ieee80211_rx_status structure for Vendor namespace information?  In my 
backports 3.14 version I used them to add some register information to 
the radiotap header in the lab. How does one use the vendor name space 
without those structure members?

Thanks for you assistance
Clyde


--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2014-11-04 19:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04 18:37 C. McPherson [this message]
2014-11-04 18:37 ` Vendor Namespace Question C. McPherson
2014-11-04 19:47 ` Johannes Berg
2014-11-04 19:47   ` Johannes Berg
2014-11-04 20:18   ` C. McPherson
2014-11-04 20:18     ` C. McPherson
2014-11-06 22:31     ` Johannes Berg
2014-11-06 22:31       ` Johannes Berg
2014-11-12 20:55       ` C. McPherson
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=54591CF9.7030106@verizon.net \
    --to=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 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.