From: Johannes Berg <johannes@sipsolutions.net>
To: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>
Cc: Zefir Kurtisi <zefir.kurtisi@neratec.com>,
linux-wireless@vger.kernel.org,
mathias.kretschmer@fokus.fraunhofer.de,
Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
Subject: Re: [PATCH] mac80211: fix recalc_radar hwconf sync problem
Date: Fri, 05 Apr 2013 13:22:51 +0200 [thread overview]
Message-ID: <1365160971.8515.23.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <20130404182219.GA24704@pandem0nium>
On Thu, 2013-04-04 at 20:22 +0200, Simon Wunderlich wrote:
> As far as I see, the problem happens when changing from a DFS to a non-DFS
> channel. local->hw.conf.radar_enabled is true from the last (DFS) channel,
> but the channel gets released when stopping the AP, and the channel context
> is freed.
At this point, why doesn't it disable hw.conf.radar_enabled? I really
think it should?
johannes
next prev parent reply other threads:[~2013-04-05 11:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 16:39 [PATCH] mac80211: fix recalc_radar hwconf sync problem Simon Wunderlich
2013-04-03 12:46 ` Johannes Berg
2013-04-04 13:38 ` Zefir Kurtisi
2013-04-04 18:22 ` Simon Wunderlich
2013-04-05 10:08 ` Zefir Kurtisi
2013-04-05 10:11 ` Zefir Kurtisi
2013-04-05 11:29 ` Simon Wunderlich
2013-04-05 12:11 ` Zefir Kurtisi
2013-04-05 11:22 ` Johannes Berg [this message]
2013-04-05 12:16 ` Simon Wunderlich
2013-04-05 12:36 ` Johannes Berg
2013-04-08 11:51 ` Simon Wunderlich
2013-04-08 12:09 ` [PATCHv2] " Simon Wunderlich
2013-04-08 14:17 ` Zefir Kurtisi
2013-04-08 14:29 ` Johannes Berg
2013-04-08 17:04 ` [PATCHv3] " Simon Wunderlich
2013-04-08 17:53 ` Antonio Quartulli
2013-04-08 20:43 ` [PATCHv4] " Simon Wunderlich
2013-04-09 9:50 ` Johannes Berg
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=1365160971.8515.23.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mathias.kretschmer@fokus.fraunhofer.de \
--cc=simon.wunderlich@s2003.tu-chemnitz.de \
--cc=siwu@hrz.tu-chemnitz.de \
--cc=zefir.kurtisi@neratec.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).