Linux wireless drivers development
 help / color / mirror / Atom feed
From: Sujith Manoharan <sujith@msujith.org>
To: linux-wireless@vger.kernel.org
Cc: ath9k-devel@qca.qualcomm.com
Subject: Re: [RFC 3/4] ath9k: Fix force_channel usage for offchannel frames
Date: Wed, 24 Sep 2014 11:19:55 +0530	[thread overview]
Message-ID: <21538.23427.487888.806826@gargle.gargle.HOWL> (raw)
In-Reply-To: <1411533452-22921-4-git-send-email-sujith@msujith.org>

Sujith Manoharan wrote:
> From: Sujith Manoharan <c_manoha@qca.qualcomm.com>
> 
> Since RoC is done before frames marked with
> IEEE80211_TX_CTL_TX_OFFCHAN are received by the driver,
> setting force_channel is useless. We will be in
> the required offchannel, so incoming frames can
> be transmitted immediately.
> 
> Signed-off-by: Sujith Manoharan <c_manoha@qca.qualcomm.com>
> ---
>  drivers/net/wireless/ath/ath9k/xmit.c | 3 ---
>  1 file changed, 3 deletions(-)
> 
> diff --git a/drivers/net/wireless/ath/ath9k/xmit.c b/drivers/net/wireless/ath/ath9k/xmit.c
> index 00931b6..4d00f59 100644
> --- a/drivers/net/wireless/ath/ath9k/xmit.c
> +++ b/drivers/net/wireless/ath/ath9k/xmit.c
> @@ -2211,9 +2211,6 @@ int ath_tx_start(struct ieee80211_hw *hw, struct sk_buff *skb,
>  	if (vif)
>  		avp = (void *)vif->drv_priv;
>  
> -	if (info->flags & IEEE80211_TX_CTL_TX_OFFCHAN)
> -		txctl->force_channel = true;
> -
>  	ret = ath_tx_prepare(hw, skb, txctl);
>  	if (ret)
>  	    return ret;

This breaks things, so this patch can be dropped.

Sujith

  reply	other threads:[~2014-09-24  5:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-24  4:37 [RFC 0/4] ath9k patches Sujith Manoharan
2014-09-24  4:37 ` [RFC 1/4] ath9k: Fix queue management Sujith Manoharan
2014-09-24  4:37 ` [RFC 2/4] ath9k: Use normal queues for offchannel frames Sujith Manoharan
2014-09-24  4:37 ` [RFC 3/4] ath9k: Fix force_channel usage " Sujith Manoharan
2014-09-24  5:49   ` Sujith Manoharan [this message]
2014-09-24  4:37 ` [RFC 4/4] ath9k: Fix offchannel queuing Sujith Manoharan

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=21538.23427.487888.806826@gargle.gargle.HOWL \
    --to=sujith@msujith.org \
    --cc=ath9k-devel@qca.qualcomm.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