netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhu Yi <yi.zhu@intel.com>
To: Jiri Benc <jbenc@suse.cz>
Cc: netdev@vger.kernel.org, "John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH 2/6] d80211: create "wifi.h" to define WIFI OUIs
Date: Fri, 15 Dec 2006 11:22:36 +0800	[thread overview]
Message-ID: <1166152956.2929.93.camel@debian.sh.intel.com> (raw)
In-Reply-To: <20061214113150.54523e61@griffin.suse.cz>

On Thu, 2006-12-14 at 11:31 +0100, Jiri Benc wrote:
> AFAIK "wifi" is a trademark and we want to avoid using it. "wlan" seems
> to be a better alternative for the prefixes. Also, I don't see a reason
> for a separate header file here.

WI-FI(r) is a trademark, but wifi and WIFI_XXX are not. I'm OK with
putting these to existed headers.

Thanks,
-yi

      reply	other threads:[~2006-12-15  3:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-14  4:02 [PATCH 2/6] d80211: create "wifi.h" to define WIFI OUIs Zhu Yi
2006-12-14 10:31 ` Jiri Benc
2006-12-15  3:22   ` Zhu Yi [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=1166152956.2929.93.camel@debian.sh.intel.com \
    --to=yi.zhu@intel.com \
    --cc=jbenc@suse.cz \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.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).