From: Dan Williams <dcbw@redhat.com>
To: yi.zhu@intel.com
Cc: netdev@vger.kernel.org, "John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH 4/7] ieee80211: Add IEEE80211_API_VERSION macro
Date: Mon, 21 Aug 2006 06:39:59 -0400 [thread overview]
Message-ID: <1156156799.5729.23.camel@localhost.localdomain> (raw)
In-Reply-To: <20060821033322.GA4793@mail.intel.com>
On Mon, 2006-08-21 at 11:33 +0800, Zhu Yi wrote:
> Add IEEE80211_API_VERSION macro so that drivers are able to check it
> during compile time. This feature is useful to make backward IEEE80211
> compatibilities for wireless drivers.
Per my other mail, what exactly has changed and must be checked? The
SIOCGIWFREQ stuff?
Dan
> Signed-off-by: Zhu Yi <yi.zhu@intel.com>
>
> ---
>
> include/net/ieee80211.h | 12 +++++++++++-
> 1 files changed, 11 insertions(+), 1 deletions(-)
>
> 29be0803256136011dd5c3b62e3eb9f782e57dbd
> diff --git a/include/net/ieee80211.h b/include/net/ieee80211.h
> index b174ebb..83e06aa 100644
> --- a/include/net/ieee80211.h
> +++ b/include/net/ieee80211.h
> @@ -29,7 +29,17 @@
> #include <linux/kernel.h> /* ARRAY_SIZE */
> #include <linux/wireless.h>
>
> -#define IEEE80211_VERSION "git-1.1.13"
> +#define IEEE80211_VERSION_MAJOR 1
> +#define IEEE80211_VERSION_API 2
> +#define IEEE80211_VERSION_MINOR 15
> +#define IEEE80211_VERSION_CODE IEEE80211_VERSION_MAJOR * 65536 + \
> + IEEE80211_VERSION_API * 256 + \
> + IEEE80211_VERSION_MINOR
> +#define _STRX(x) #x
> +#define _VERSION_STR(a,b,c) _STRX(a) "." _STRX(b) "." _STRX(c)
> +#define IEEE80211_VERSION _VERSION_STR(IEEE80211_VERSION_MAJOR,\
> + IEEE80211_VERSION_API, \
> + IEEE80211_VERSION_MINOR)
>
> #define IEEE80211_DATA_LEN 2304
> /* Maximum size for the MA-UNITDATA primitive, 802.11 standard section
next prev parent reply other threads:[~2006-08-21 10:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-21 3:33 [PATCH 4/7] ieee80211: Add IEEE80211_API_VERSION macro Zhu Yi
2006-08-21 10:39 ` Dan Williams [this message]
2006-08-22 4:50 ` Zhu Yi
2006-08-21 13:02 ` Christoph Hellwig
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=1156156799.5729.23.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=yi.zhu@intel.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 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).