From: Karl Beldan <karl.beldan@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Karl Beldan <karl.beldan@rivierawaves.com>
Subject: Re: [RFC 1/2] mac80211: Use a cfg80211_chan_def in ieee80211_hw_conf_chan
Date: Mon, 18 Mar 2013 22:38:33 +0100 [thread overview]
Message-ID: <20130318213833.GA25758@gobelin> (raw)
In-Reply-To: <1363634710.8260.15.camel@jlt4.sipsolutions.net>
On Mon, Mar 18, 2013 at 08:25:10PM +0100, Johannes Berg wrote:
> On Sun, 2013-03-17 at 21:30 +0100, Karl Beldan wrote:
>
> > + if (conf->chandef.chan)
>
> > + else
> > + wiphy_debug(hw->wiphy,
> > + "%s (freq=0/%s idle=%d ps=%d smps=%s)\n",
>
> I don't think the else should be allowed to happen.
>
> > --- a/net/mac80211/cfg.c
> > +++ b/net/mac80211/cfg.c
> > @@ -805,8 +805,7 @@ static int ieee80211_set_monitor_channel(struct wiphy *wiphy,
> > IEEE80211_CHANCTX_EXCLUSIVE);
> > }
> > } else if (local->open_count == local->monitors) {
> > - local->_oper_channel = chandef->chan;
> > - local->_oper_channel_type = cfg80211_get_chandef_type(chandef);
> > + memcpy(&local->oper_chandef, chandef, sizeof(local->oper_chandef));
>
> Somehow I'd prefer an assignment:
>
> local->oper_chandef = *chandef;
>
> I know it'll just be a memcpy() again, but ... reads nicer, imho.
>
> > + memcpy(chandef, &local->oper_chandef, sizeof(chandef));
>
> ditto
>
> > @@ -22,7 +22,9 @@ static void ieee80211_change_chanctx(struct ieee80211_local *local,
> > drv_change_chanctx(local, ctx, IEEE80211_CHANCTX_CHANGE_WIDTH);
> >
> > if (!local->use_chanctx) {
> > - local->_oper_channel_type = cfg80211_get_chandef_type(chandef);
> > + local->oper_chandef.width = chandef->width;
> > + local->oper_chandef.center_freq1 = chandef->center_freq1;
> > + local->oper_chandef.center_freq2 = chandef->center_freq2;
>
> Why not assign all here as well? Is the channel pointer itself special?
>
> > - /* For backward compatibility only -- do not use */
> > - struct ieee80211_channel *_oper_channel;
> > - enum nl80211_channel_type _oper_channel_type;
> > + struct cfg80211_chan_def oper_chandef;
>
> You shouldn't remove the comment, and I think you should also keep the
> leading underscore -- this is still for backward compatibility with
> non-chanctx drivers only, and mac80211 internally must use chanctxes all
> the way except in SW scan and SW roc code.
>
> > +static int ieee80211_chandef_cmp(const struct cfg80211_chan_def *def1,
> > + const struct cfg80211_chan_def *def2)
>
> indentation
>
> However this already exists in cfg80211.h --
> cfg80211_chandef_identical().
>
cfg80211_chandef_identical() will compare the whole chandef whatever the
channel width.
Karl
next prev parent reply other threads:[~2013-03-18 21:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-17 20:30 [RFC 0/2] mac80211: Enable VHT for non chanctxes drivers Karl Beldan
2013-03-17 20:30 ` [RFC 1/2] mac80211: Use a cfg80211_chan_def in ieee80211_hw_conf_chan Karl Beldan
2013-03-17 21:28 ` Karl Beldan
2013-03-18 19:25 ` Johannes Berg
2013-03-18 19:46 ` Karl Beldan
2013-03-18 21:14 ` Karl Beldan
2013-03-18 21:25 ` Johannes Berg
2013-03-18 21:38 ` Karl Beldan [this message]
2013-03-19 18:24 ` Johannes Berg
2013-03-19 18:29 ` Karl Beldan
2013-03-19 12:53 ` Karl Beldan
2013-03-19 0:12 ` Karl Beldan
2013-03-17 20:30 ` [RFC 2/2] mac80211: Let drivers not supporting channel contexts use VHT Karl Beldan
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=20130318213833.GA25758@gobelin \
--to=karl.beldan@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=karl.beldan@rivierawaves.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).