stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Benjamin Berg <benjamin@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org,
	kvalo@qca.qualcomm.com, mathias.kretschmer@fokus.fraunhofer.de,
	stable@vger.kernel.org, sw@simonwunderlich.de
Subject: Re: [PATCH] ath9k: Prevent radard detection and spectral scan to be used concurrently
Date: Tue, 2 Jun 2015 10:25:04 +0900	[thread overview]
Message-ID: <20150602012504.GC23370@kroah.com> (raw)
In-Reply-To: <1433182357-17405-1-git-send-email-benjamin@sipsolutions.net>

On Mon, Jun 01, 2015 at 08:12:37PM +0200, Benjamin Berg wrote:
> In the case that a spectral scan is enabled the PHY errors sent by the
> hardware as part of the scanning might trigger the radar detection and
> channels might be marked as 'unusable' incorrectly. This patch fixes
> the issue by preventing the spectral scan to be enabled if DFS is used
> and only analysing the PHY errors for DFS if radar detection is enabled.
> 
> Reported-by: Mathias Kretschmer <mathias.kretschmer@fokus.fraunhofer.de>
> Signed-off-by: Benjamin Berg <benjamin@sipsolutions.net>
> Signed-off-by: Simon Wunderlich <sw@simonwunderlich.de>
> 
> [v3.19+]
> ---
> 
> The patch does apply to 3.19+ with a bit of fuzz.
> 
> 
>  drivers/net/wireless/ath/ath9k/common-spectral.c | 4 ++++
>  drivers/net/wireless/ath/ath9k/main.c            | 6 ++++++
>  drivers/net/wireless/ath/ath9k/recv.c            | 7 +++++--
>  3 files changed, 15 insertions(+), 2 deletions(-)
> 

<formletter>

This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read Documentation/stable_kernel_rules.txt
for how to do this properly.

</formletter>

      reply	other threads:[~2015-06-02  1:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-01 18:12 [PATCH] ath9k: Prevent radard detection and spectral scan to be used concurrently Benjamin Berg
2015-06-02  1:25 ` Greg KH [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=20150602012504.GC23370@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=benjamin@sipsolutions.net \
    --cc=kvalo@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mathias.kretschmer@fokus.fraunhofer.de \
    --cc=stable@vger.kernel.org \
    --cc=sw@simonwunderlich.de \
    /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).