linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven.eckelmann@openmesh.com>
To: Manikanta Pubbisetty <mpubbise@codeaurora.org>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
	simon.wunderlich@openmesh.com,
	"Daniel Bailey" <daniel.bailey@openmesh.com>,
	"Shashidhar Lakkavalli" <shashidhar.lakkavalli@openmesh.com>,
	linux-wireless@vger.kernel.org
Subject: Re: mac80211: AQM and block_tx
Date: Tue, 10 Jul 2018 15:40:53 +0200	[thread overview]
Message-ID: <127626548.T5BRAgXPx7@bentobox> (raw)
In-Reply-To: <51cebb7e-52cf-0421-a4c9-cad7a6f30035@codeaurora.org>

[-- Attachment #1: Type: text/plain, Size: 533 bytes --]

On Dienstag, 10. Juli 2018 18:09:37 CEST Manikanta Pubbisetty wrote:
[...]
> I am working on a patch which takes care of stopping the iTXQs after 
> detecting a radar(covering other scenarios where stopping iTXQs is 
> important)
> and there by making sure packets are not transmitted.
[...]
> https://patchwork.kernel.org/patch/10516887/

Thanks for telling me about this patch. It indeed prevents the unwanted TX 
during CSA (and thanks for the explanation in the commit message about the 
underlying problem).

Kind regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2018-07-10 13:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-05  8:47 mac80211: AQM and block_tx Sven Eckelmann
2018-07-10  6:55 ` Sven Eckelmann
2018-07-10 12:09   ` Toke Høiland-Jørgensen
2018-07-10 12:39   ` Manikanta Pubbisetty
2018-07-10 13:40     ` Sven Eckelmann [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=127626548.T5BRAgXPx7@bentobox \
    --to=sven.eckelmann@openmesh.com \
    --cc=daniel.bailey@openmesh.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mpubbise@codeaurora.org \
    --cc=shashidhar.lakkavalli@openmesh.com \
    --cc=simon.wunderlich@openmesh.com \
    --cc=toke@toke.dk \
    /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).