linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Wunderlich <sw@simonwunderlich.de>
To: Luciano Coelho <luciano.coelho@intel.com>
Cc: linux-wireless@vger.kernel.org, yeohchunyeow@gmail.com,
	yeohchunyeow@cozybit.com
Subject: Re: [PATCH v9 0/5] CSA Beacon Count changes
Date: Fri, 13 Dec 2013 18:23:35 +0100	[thread overview]
Message-ID: <201312131823.35206.sw@simonwunderlich.de> (raw)
In-Reply-To: <1386935675-24548-1-git-send-email-luciano.coelho@intel.com>

Hey Luca,

> Hi,
> 
> More changes, hopefully the last ones for this series. ;)
> 
> I have hacked wpa_supplicant to support CSA in IBSS, so I could test
> it too.  I created some ma80211_hwsim testcases on top of this.  The
> tests now pass, though I get some semi-random WARNs [1] when using 3
> stations.  It seems to be a race condition and it doesn't seem to be
> related to this series, so I think we should address it separately
> (Simon, hint! ;).
> 
> I have also created some basic BSS CSA test cases for mac80211_hwsim.
> The tests pass, except when I try count < 2, which is expected, since
> we did not implement the CSA action frame in BSS mode.
> 
> I'll upstream the BSS CSA test cases soon.  The IBSS test cases still
> need to be cleaned up (actually they're worthless without the IBSS CSA
> support in wpa_supplicant, which needs to be cleaned up).  If someone
> is interested in this, let me know and I can send them
> "without-warranty of any kind". ;)
> 
> Please review and test!

Patches look good to me and worked fine in my test environment. Everything as 
expected for CSA counts of 0, 1, 2 and 10, no warnings or weird behaviour. 
I've tested with two stations in IBSS mode using ath9k.

So, apart from that function name issue, feel free to add for Patch 1,2 and 5:

Acked-by/Tested-by: Simon Wunderlich <sw@simonwunderlich.de>

I'll try to reproduce the issue you were seeing when these testcases/wpa_s 
implementation are upstream (or patches are available). I didn't see the 
problem on a first glance, but the warning is not critical (basically the CSA 
will fail), so I guess it's OK to fix it soon[tm].

Thanks for your work!
   Simon

  parent reply	other threads:[~2013-12-13 17:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-13 11:54 [PATCH v9 0/5] CSA Beacon Count changes Luciano Coelho
2013-12-13 11:54 ` [PATCH v9 1/5] mac80211: refactor ieee80211_ibss_process_chanswitch() Luciano Coelho
2013-12-13 11:54 ` [PATCH v9 2/5] mac80211: align ieee80211_ibss_csa_beacon() with ieee80211_csa_beacon() Luciano Coelho
2013-12-13 17:12   ` Simon Wunderlich
2013-12-13 19:09     ` Coelho, Luciano
2013-12-13 11:54 ` [PATCH v9 3/5] mac80211: refactor ieee80211_mesh_process_chanswitch() Luciano Coelho
2013-12-13 11:54 ` [PATCH v9 4/5] mac80211: align ieee80211_mesh_csa_beacon() with ieee80211_csa_beacon() Luciano Coelho
2013-12-13 11:54 ` [PATCH v9 5/5] mac80211: only set CSA beacon when at least one beacon must be transmitted Luciano Coelho
2013-12-13 12:34 ` [PATCH v9 0/5] CSA Beacon Count changes Luca Coelho
2013-12-13 17:23 ` Simon Wunderlich [this message]
2013-12-13 19:10   ` Coelho, Luciano

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=201312131823.35206.sw@simonwunderlich.de \
    --to=sw@simonwunderlich.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luciano.coelho@intel.com \
    --cc=yeohchunyeow@cozybit.com \
    --cc=yeohchunyeow@gmail.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).