linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John Linville <linville@tuxdriver.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v3] cfg80211: add flags for off-channel capabilities
Date: Sun, 20 Nov 2011 17:06:17 +0200	[thread overview]
Message-ID: <4EC91769.6040105@qca.qualcomm.com> (raw)
In-Reply-To: <1321626828.10266.60.camel@jlt3.sipsolutions.net>

On 11/18/2011 04:33 PM, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
> 
> Currently mac80211 implements these for all devices,
> but given restrictions of some devices that isn't
> really true, so prepare for being able to remove the
> capability for some mac80211 devices.
> 
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>

[...]

> --- a/drivers/net/wireless/ath/ath6kl/init.c	2011-11-18 09:47:37.000000000 +0100
> +++ b/drivers/net/wireless/ath/ath6kl/init.c	2011-11-18 09:47:38.000000000 +0100
> @@ -1603,7 +1603,8 @@ int ath6kl_core_init(struct ath6kl *ar)
>  		ar->conf_flags |= ATH6KL_CONF_SUSPEND_CUTPOWER;
>  
>  	ar->wiphy->flags |= WIPHY_FLAG_SUPPORTS_FW_ROAM |
> -			    WIPHY_FLAG_HAVE_AP_SME;
> +			    WIPHY_FLAG_HAVE_AP_SME |
> +			    WIPHY_FLAG_HAS_REMAIN_ON_CHANNEL;

For the ath6kl part:

Acked-by: Kalle Valo <kvalo@qca.qualcomm.com>

Kalle

      reply	other threads:[~2011-11-20 15:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-17  9:39 [PATCH] cfg80211: add flags for off-channel capabilities Johannes Berg
2011-11-18  8:52 ` [PATCH v2] " Johannes Berg
2011-11-18 14:33   ` [PATCH v3] " Johannes Berg
2011-11-20 15:06     ` Kalle Valo [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=4EC91769.6040105@qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).