Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Karl Beldan <karl.beldan@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	Karl Beldan <karl.beldan@rivierawaves.com>
Subject: Re: [RFC V3 1/2] mac80211: Use a cfg80211_chan_def in ieee80211_hw_conf_chan
Date: Fri, 22 Mar 2013 22:08:19 +0100	[thread overview]
Message-ID: <1363986499.8238.68.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1363967304-4394-1-git-send-email-karl.beldan@gmail.com> (sfid-20130322_165146_376383_D7D32205)

On Fri, 2013-03-22 at 16:48 +0100, Karl Beldan wrote:

> +		if (chandef.chan == local->_oper_chandef.chan)
> +			chandef = local->_oper_chandef;
> +		else {
> +			chandef.width = NL80211_CHAN_WIDTH_20_NOHT;
> +			chandef.center_freq1 = chandef.chan->center_freq;
> +		}

I'll agree with checkpatch that you should probably put braces against
both arms of the if :)

> -	if (chan != local->_oper_channel ||
> -	    channel_type != local->_oper_channel_type)
> +		chandef.chan = local->tmp_channel;
> +		chandef.width = NL80211_CHAN_WIDTH_20_NOHT;
> +		chandef.center_freq1 = chandef.chan->center_freq;
> +	} else
> +		chandef = local->_oper_chandef;

same here I guess

> +	/*
> +	 * FIXME: Here we are downgrading to NL80211_CHAN_WIDTH_20_NOHT
> +	 * and don't adjust our ht/vht settings
> +	 * This is wrong - we should behave according to the CSA params
> +	 */

I can live with this in this patch. I know we need to fix it, but I
don't want to do it in this patch nor do I really want to require it for
this patch. If you feel it's a requirement for this feel free to pick up
my other patches, but then I'd prefer you did it in a separate patch.

> - out:
> +out:

that seems a little unnecessary :)

>  #define CHANDEF_ASSIGN(c)							\
> -			__entry->chan_width = (c)->width;			\
> -			__entry->center_freq1 = (c)->center_freq1;		\
> +			__entry->chan_width = (c)->width;				\
> +			__entry->center_freq1 = (c)->center_freq1;			\

hmm, why did these lines change?

johannes


  parent reply	other threads:[~2013-03-22 21:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-22 15:48 [RFC V3 1/2] mac80211: Use a cfg80211_chan_def in ieee80211_hw_conf_chan Karl Beldan
2013-03-22 15:48 ` [RFC V3 2/2] mac80211: Let drivers not supporting channel contexts use VHT Karl Beldan
2013-03-22 21:08 ` Johannes Berg [this message]
2013-03-23  0:09   ` [RFC V3 1/2] mac80211: Use a cfg80211_chan_def in ieee80211_hw_conf_chan 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=1363986499.8238.68.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=karl.beldan@gmail.com \
    --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