linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Zhu Yi <yi.zhu@intel.com>
Cc: Michael Wu <flamingice@sourmilk.net>, linux-wireless@vger.kernel.org
Subject: Re: [TAKE 2][PATCH 0/3] IEEE802.11e/WMM TS management and DLS support
Date: Mon, 11 Jun 2007 15:05:56 -0400	[thread overview]
Message-ID: <20070611190556.GF10397@tuxdriver.com> (raw)
In-Reply-To: <1180659895.3109.104.camel@debian.sh.intel.com>

On Fri, Jun 01, 2007 at 09:04:54AM +0800, Zhu Yi wrote:
> On Thu, 2007-05-31 at 12:55 -0700, Michael Wu wrote:
> > This is nowhere near ready to go upstream and it requires some bits
> > from the 802.11n patches which didn't make it. 
> 
> Can you speak what is needed for 11n and where to find the 11n patches?

The .11n patches submitted by Intel are available in wireless-dev.
The mac80211 component maintainers don't like them, and since there
is no driver for .11n hardware currently in the mainline kernel
there has not been much impetus to get the patches mainstreamed.
Perhaps when the iwlwifi driver is whipped into shape for upstream
then we will have the necessary motivation?

FWIW, I don't think there has been a very clear discussion about
the .11n patches from Intel.  They need both a more clear defense
from the authors at Intel and a more concrete set of objections
(and hopefully suggestions for improvements that lead to acceptance)
from the mac80211 component team.

Hth!

John
-- 
John W. Linville
linville@tuxdriver.com

  reply	other threads:[~2007-06-11 19:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-25 11:52 [TAKE 2][PATCH 0/3] IEEE802.11e/WMM TS management and DLS support Zhu Yi
2007-05-31 18:04 ` John W. Linville
2007-05-31 19:55   ` Michael Wu
2007-06-01  1:04     ` Zhu Yi
2007-06-11 19:05       ` John W. Linville [this message]
2007-06-01  1:01   ` Zhu Yi

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=20070611190556.GF10397@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=flamingice@sourmilk.net \
    --cc=linux-wireless@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).