public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Orr Mazor <orr.mazor@tandemg.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	"linux-wireless\@vger.kernel.org"
	<linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] subsystem: Fix radar event during another phy CAC
Date: Wed, 15 Jan 2020 09:40:37 +0200	[thread overview]
Message-ID: <87d0bl1822.fsf@tynnyri.adurom.net> (raw)
In-Reply-To: <20191222145449.15792-1-Orr.Mazor@tandemg.com> (Orr Mazor's message of "Sun, 22 Dec 2019 14:55:31 +0000")

Orr Mazor <orr.mazor@tandemg.com> writes:

> In case a radar event of CAC_FINISHED or RADAR_DETECTED
> happens during another phy is during CAC we might need
> to cancel that CAC.
> If we got a radar in a channel that another phy is now
> doing CAC on then the CAC should be canceled.
> If, for example, 2 phys doing CAC on the same channels,
> or on comptable channels, once on of them will finish his CAC
> the other might need to cancel his CAC, since it is no
> longer relevant.
>
> To fix that the commit adds an callback and implement it in mac80211
> to end CAC.
> This commit also adds a call to said callback if after a radar
> event we see the cac is no longer relevant
>
> Signed-off-by: Orr Mazor <Orr.Mazor@tandemg.com>

The title prefix should be "cfg80211: ", not "subsystem: ".

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

  parent reply	other threads:[~2020-01-15  7:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-22 14:55 [PATCH] subsystem: Fix radar event during another phy CAC Orr Mazor
2019-12-23 10:52 ` Sergey Matyukevich
2019-12-24  8:29   ` Orr Mazor
2019-12-24 11:42     ` Sergey Matyukevich
2019-12-24 13:18       ` Orr Mazor
2019-12-24 15:37         ` Sergey Matyukevich
2020-01-15  7:40 ` Kalle Valo [this message]
2020-01-15 10:28   ` Johannes Berg

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=87d0bl1822.fsf@tynnyri.adurom.net \
    --to=kvalo@codeaurora.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=orr.mazor@tandemg.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