From: Johannes Berg <johannes@sipsolutions.net>
To: Eliad Peller <eliad@wizery.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/3] mac80211: consider only relevant vifs for radar_required calculation
Date: Tue, 06 Jan 2015 15:05:11 +0100 [thread overview]
Message-ID: <1420553111.1966.32.camel@sipsolutions.net> (raw)
In-Reply-To: <1420542274.1966.21.camel@sipsolutions.net> (sfid-20150106_120447_628454_273C3B51)
On Tue, 2015-01-06 at 12:04 +0100, Johannes Berg wrote:
> all three applied.
Nope, dropped patch 2 again - it was causing issues when running the
hwsim tests:
$ ./vm-run.sh dfs ap_ht_40mhz_intolerant_ap
Starting test run in a virtual machine
./run-all.sh: passing the following args to run-tests.py: dfs
ap_ht_40mhz_intolerant_ap
START dfs 1/2
19
703
PASS dfs 65.148949 2015-01-06 14:02:54.263314
START ap_ht_40mhz_intolerant_ap 2/2
19
719
command failed: Device or resource busy (-16)
Exception: AP startup failed
FAIL ap_ht_40mhz_intolerant_ap 15.53641 2015-01-06 14:03:09.842131
failed tests: ap_ht_40mhz_intolerant_ap
Maybe the tests don't clean up properly, or something, but I'm not going
to investigate this now.
johannes
next prev parent reply other threads:[~2015-01-06 14:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-04 10:13 [PATCH 1/3] mac80211: consider only relevant vifs for radar_required calculation Eliad Peller
2015-01-04 10:13 ` [PATCH 2/3] mac80211: don't defer scans in case of radar detection Eliad Peller
2015-01-04 10:13 ` [PATCH 3/3] mac80211: always recalc_radar on chanctx changes Eliad Peller
2015-01-06 11:04 ` [PATCH 1/3] mac80211: consider only relevant vifs for radar_required calculation Johannes Berg
2015-01-06 14:05 ` Johannes Berg [this message]
2015-01-06 14:14 ` Johannes Berg
2015-01-06 18:57 ` Eliad Peller
2015-01-06 19:02 ` Johannes Berg
2015-01-06 19:36 ` Eliad Peller
2015-01-07 15:58 ` Eliad Peller
2015-01-07 16:32 ` Johannes Berg
2015-01-07 16:42 ` Eliad Peller
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=1420553111.1966.32.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=eliad@wizery.com \
--cc=linux-wireless@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).