linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Bianconi <lorenzo@kernel.org>
To: kvalo@codeaurora.org
Cc: lorenzo.bianconi@redhat.com, linux-wireless@vger.kernel.org,
	koen.vandeputte@ncentric.com
Subject: [PATCH 0/4] ath9k: dynack: fixes + cleanup
Date: Tue, 20 Aug 2019 18:20:18 +0200	[thread overview]
Message-ID: <cover.1566317488.git.lorenzo@kernel.org> (raw)

Improve ath9k dynack reliability in p2p/p2mp dynamic topologies.
Improve code readability removing duplicated code.
This series has been tested by Koen Vandeputte on multiple outdoor
links/devices.
This series is based on 'ath9k: dynack: fix possible deadlock in
ath_dynack_node_{de}init'
https://patchwork.kernel.org/patch/11100409/

Lorenzo Bianconi (4):
  ath9k: dyanck: introduce ath_dynack_set_timeout routine
  ath9k: dynack: properly set last timeout timestamp in ath_dynack_reset
  ath9k: dynack: set max timeout according to channel width
  ath9k: dynack: set ackto to max timeout in ath_dynack_reset

 drivers/net/wireless/ath/ath9k/dynack.c | 93 +++++++++++++++++--------
 1 file changed, 63 insertions(+), 30 deletions(-)

-- 
2.21.0


             reply	other threads:[~2019-08-20 16:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-20 16:20 Lorenzo Bianconi [this message]
2019-08-20 16:20 ` [PATCH 1/4] ath9k: dyanck: introduce ath_dynack_set_timeout routine Lorenzo Bianconi
2019-09-04  6:20   ` Kalle Valo
2019-08-20 16:20 ` [PATCH 2/4] ath9k: dynack: properly set last timeout timestamp in ath_dynack_reset Lorenzo Bianconi
2019-08-20 16:20 ` [PATCH 3/4] ath9k: dynack: set max timeout according to channel width Lorenzo Bianconi
2019-08-20 16:20 ` [PATCH 4/4] ath9k: dynack: set ackto to max timeout in ath_dynack_reset Lorenzo Bianconi

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=cover.1566317488.git.lorenzo@kernel.org \
    --to=lorenzo@kernel.org \
    --cc=koen.vandeputte@ncentric.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo.bianconi@redhat.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).