All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Sowmiya Sree Elavalagan <ssreeela@codeaurora.org>
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
	Lei Wang <leiwa@codeaurora.org>,
	Sowmiya Sree Elavalagan <ssreeela@codeaurora.org>
Subject: Re: [PATCH] ath10k: enable radar detection in secondary segment
Date: Thu, 26 Mar 2020 10:01:39 +0000 (UTC)	[thread overview]
Message-ID: <20200326100139.3B27FC43636@smtp.codeaurora.org> (raw)
In-Reply-To: <1585158041-11740-1-git-send-email-ssreeela@codeaurora.org>

Sowmiya Sree Elavalagan <ssreeela@codeaurora.org> wrote:

> From: Lei Wang <leiwa@codeaurora.org>
> 
> Enable radar detection in secondary segment for VHT160 and VHT80+80 mode
> on DFS channels. Otherwise, when injecting radar pulse in the secondary
> segment, the DUT can't detect radar pulse.
> 
> Tested: qca9984 with firmware ver 10.4-3.10-00047
> 
> Signed-off-by: Lei Wang <leiwa@codeaurora.org>
> Signed-off-by: Sowmiya Sree Elavalagan <ssreeela@codeaurora.org>

Failed to apply:

error: patch failed: drivers/net/wireless/ath/ath10k/wmi.c:1717
error: drivers/net/wireless/ath/ath10k/wmi.c: patch does not apply
stg import: Diff does not apply cleanly

Patch set to Changes Requested.

-- 
https://patchwork.kernel.org/patch/11458405/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

      parent reply	other threads:[~2020-03-26 10:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25 17:40 [PATCH] ath10k: enable radar detection in secondary segment Sowmiya Sree Elavalagan
2020-03-25 17:40 ` Sowmiya Sree Elavalagan
2020-03-26 10:01 ` Kalle Valo
2020-03-26 10:05   ` Kalle Valo
2020-03-26 10:05     ` Kalle Valo
2020-03-26 13:19     ` ssreeela
2020-03-26 13:19       ` ssreeela
2020-03-26 10:01 ` 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=20200326100139.3B27FC43636@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=ath10k@lists.infradead.org \
    --cc=leiwa@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=ssreeela@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.