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: Tue, 06 Jan 2015 20:02:56 +0100 [thread overview]
Message-ID: <1420570976.1966.34.camel@sipsolutions.net> (raw)
In-Reply-To: <CAB3XZEctcBuPG6f4ZrZFV5O3Z7+hi+ShFdwvFXdJovG2KeAufQ@mail.gmail.com> (sfid-20150106_195729_910977_930DB9CB)
On Tue, 2015-01-06 at 20:57 +0200, Eliad Peller wrote:
> On Tue, Jan 6, 2015 at 4:14 PM, Johannes Berg <johannes@sipsolutions.net> wrote:
> > On Tue, 2015-01-06 at 15:05 +0100, Johannes Berg wrote:
> >> On Tue, 2015-01-06 at 12:04 +0100, Johannes Berg wrote:
> >> > all three applied.
> >>
> >> Nope, dropped patch 2 again
> >
> > And dropped the other two also - with them the sequence of two tests I
> > was looking at never completes.
> >
> err... sorry about that.
> i'll look into it.
I think there's probably two bugs - the test suite should wait for all
the DFS stuff to finish.
But the fact that it never completes now is strange, maybe somehow radar
detection doesn't get turned off properly after your patches?
johannes
next prev parent reply other threads:[~2015-01-06 19:03 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 [this message]
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=1420570976.1966.34.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.