From: Luca Coelho <luca@coelho.fi>
To: "johannes@sipsolutions.net" <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"janusz.dziedzic@tieto.com" <janusz.dziedzic@tieto.com>,
"eliad@wizery.com" <eliad@wizery.com>
Subject: Re: [PATCH] cfg80211: fix start_radar_detection issue
Date: Thu, 15 May 2014 12:55:37 +0300 [thread overview]
Message-ID: <1400147737.4521.11.camel@dubbel> (raw)
In-Reply-To: <1400147514.4521.10.camel@dubbel>
On Thu, 2014-05-15 at 09:51 +0000, Coelho, Luciano wrote:
> On Thu, 2014-05-15 at 11:39 +0200, Johannes Berg wrote:
> > On Thu, 2014-05-15 at 12:28 +0300, Eliad Peller wrote:
> > > On Wed, May 14, 2014 at 5:42 PM, Johannes Berg
> > > <johannes@sipsolutions.net> wrote:
> > > > On Wed, 2014-05-14 at 13:25 +0200, Janusz Dziedzic wrote:
> > > >> After patch:
> > > >> cfg80211/mac80211: refactor cfg80211_chandef_dfs_required()
> > > >>
> > > >> start_radar_detection always fail with -EINVAL.
> > > >
> > > > Applied, thanks.
> > > >
> > > probably a bit late, but i don't really see why passing
> > > NL80211_IFTYPE_UNSPECIFIED at all, instead of the iftype?
> >
> > I did briefly wonder about the same, but decided Luca probably knew
> > better :)
>
> Actually I also thought the same thing, but had the impression that
> there were cases when we wouldn't have the iftype when calling this.
> But now I checked both cases where we use NL80211_IFTYPE_UNSPECIFIED and
> it seems that we really don't need it.
>
> I'll send a patch to fix this and revert Janusz's change (unless
> Johannes wants to rebase the mac80211-next tree).
Instead of just reverting Janusz's patch, I'll make
cfg80211_chandef_dfs_required() WARN if UNSPECIFIED is passed.
--
Luca.
prev parent reply other threads:[~2014-05-15 9:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 11:25 [PATCH] cfg80211: fix start_radar_detection issue Janusz Dziedzic
2014-05-14 12:43 ` Coelho, Luciano
2014-05-14 14:42 ` Johannes Berg
2014-05-15 9:28 ` Eliad Peller
2014-05-15 9:39 ` Johannes Berg
2014-05-15 9:51 ` Coelho, Luciano
2014-05-15 9:55 ` Luca Coelho [this message]
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=1400147737.4521.11.camel@dubbel \
--to=luca@coelho.fi \
--cc=eliad@wizery.com \
--cc=janusz.dziedzic@tieto.com \
--cc=johannes@sipsolutions.net \
--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