linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhu Yi <yi.zhu@intel.com>
To: Michael Wu <flamingice@sourmilk.net>
Cc: jketreno <jketreno@linux.intel.com>, Jiri Benc <jbenc@suse.cz>,
	"John W. Linville" <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org
Subject: Re: IEEE802.11e/WMM TS management and DLS support
Date: Fri, 08 Jun 2007 10:42:39 +0800	[thread overview]
Message-ID: <1181270559.3039.119.camel@debian.sh.intel.com> (raw)
In-Reply-To: <200706071540.41665.flamingice@sourmilk.net>

On Thu, 2007-06-07 at 15:40 -0700, Michael Wu wrote:
> Sure. But frankly, this code sucks. The original patch that I reviewed had 
> problems that indicated a total lack of testing.. and that was just for a 
> subset of the patch series that I actually reviewed in detail. Even the 
> design of the entire patch series is questionable even if we weren't trying 
> to move to a userspace MLME (and we need to, because kernel space MLME is a 
> *dead end*).

user space MLME is good, I'd also agree to move to it if it is ready.
But the key point for the patch series is not dealing with MLME. They
are about the TS managment and DLS. Please concentrate on the key point.
Did you ever read IEEE 802.11e or WMM specs?

>  The patch series also introduced sparse errors.

$ cd wireless-dev.git
$ touch net/mac80211/*.[ch]
$ make modules C=1

Sparse does generate a lot of errors. But there is only one from my
patches (because I define int dls_sta:1 which is followed the int
assoc_ap:1 defined already there).

> Do I need to go on? Make the code suck less and we won't have to go through 
> this again. It's that simple. It's not about being aggressive or offensive. 
> It's about having some standards.
> 
> Now of course, this also happened because Linville didn't see much and assumed 
> it was okay. If a patch needs review (and a patch series of this size *needs* 
> review), go ahead and ask for a review (or remind me I need to do one!). I 
> don't have much time this summer for writing code, but I will make sure I 
> have time to review code, especially if Jiri Benc is not around.

I have addressed all your comments in this series, right? And you are in
the cc list. You have more, just speak out!

-yi

  reply	other threads:[~2007-06-08  2:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-06  8:21 IEEE802.11e/WMM TS management and DLS support Zhu Yi
2007-06-06 20:00 ` Johannes Berg
2007-06-08  8:16   ` Zhu Yi
2007-06-08  9:30     ` Johannes Berg
2007-06-08 13:35       ` Cohen, Guy
2007-06-07 20:43 ` Jiri Benc
2007-06-08  3:52   ` jketreno
2007-06-07 21:12     ` Michael Wu
2007-06-08  4:41       ` jketreno
2007-06-07 22:40         ` Jiri Benc
2007-06-08  1:53           ` Zhu Yi
2007-06-07 22:40         ` Michael Wu
2007-06-08  2:42           ` Zhu Yi [this message]
2007-06-12 14:02   ` John W. Linville

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=1181270559.3039.119.camel@debian.sh.intel.com \
    --to=yi.zhu@intel.com \
    --cc=flamingice@sourmilk.net \
    --cc=jbenc@suse.cz \
    --cc=jketreno@linux.intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).