From: Johannes Berg <johannes@sipsolutions.net>
To: Eliad Peller <eliad@wizery.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/3] mac80211: consider only relevant vifs for radar_required calculation
Date: Wed, 07 Jan 2015 17:32:38 +0100 [thread overview]
Message-ID: <1420648358.3407.19.camel@sipsolutions.net> (raw)
In-Reply-To: <CAB3XZEdJw=vaLVO+5YXkH1ZPerKYC4s-_+E0nzL+XUXMiZQLkw@mail.gmail.com> (sfid-20150107_165842_207074_75213483)
On Wed, 2015-01-07 at 17:58 +0200, Eliad Peller wrote:
> ok, sent a new patchset.
>
> there were some missing updates of local->radar_detect_enabled, so i
> preferred to simply remove it altogether and check for radar detection
> directly when needed (i.e. on scan/roc).
Sounds good, thanks.
> ap_ht_40mhz_intolerant_ap still seems to fail here, but it fails even
> when running only this test, without any of my patches applied.
> now i get the same error with my patches applied ("Exception: AP did
> not move to 40 MHz channel") instead of the EBUSY one.
>
> i'll try debugging this issue as well.
Well, if you want to :)
It's not related to your patches I think, and I saw it passing w/o your
patches applied.
johannes
next prev parent reply other threads:[~2015-01-07 16:32 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
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 [this message]
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=1420648358.3407.19.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.