netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Zhu Yi <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 14:02:51 +0100	[thread overview]
Message-ID: <20060821130251.GA26513@infradead.org> (raw)
In-Reply-To: <20060821033322.GA4793@mail.intel.com>

On Mon, Aug 21, 2006 at 11:33:22AM +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.

NACK.


      parent reply	other threads:[~2006-08-21 13:03 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
2006-08-22  4:50   ` Zhu Yi
2006-08-21 13:02 ` Christoph Hellwig [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=20060821130251.GA26513@infradead.org \
    --to=hch@infradead.org \
    --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).