Linux wireless drivers development
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Felix Fietkau <nbd@nbd.name>
Cc: <linux-wireless@vger.kernel.org>, <kvalo@codeaurora.org>
Subject: Re: [v2,1/3] ath9k: rename tx_complete_work to hw_check_work
Date: Tue, 7 Feb 2017 01:01:07 -0800	[thread overview]
Message-ID: <b4d288b79fd544a58b9571e06e9fa1c0@eusanexr01a.eu.qualcomm.com> (raw)
In-Reply-To: <20170202091452.11939-1-nbd@nbd.name>

Felix Fietkau <nbd@nbd.name> wrote:
> Also include common MAC alive check. This should make the hang checks
> more reliable for modes where beacons are not sent and is used as a
> starting point for further hang check improvements
> 
> Signed-off-by: Felix Fietkau <nbd@nbd.name>

3 patches applied to ath-next branch of ath.git, thanks.

d63ffc45c5d3 ath9k: rename tx_complete_work to hw_check_work
a34d0a0da1ab ath9k_hw: check if the chip failed to wake up
3a5e969bb2f6 ath9k: fix race condition in enabling/disabling IRQs

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

Documentation about submitting wireless patches and checking status
from patchwork:

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

      parent reply	other threads:[~2017-02-07  9:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-02  9:14 [PATCH v2 1/3] ath9k: rename tx_complete_work to hw_check_work Felix Fietkau
2017-02-02  9:14 ` [PATCH v2 2/3] ath9k_hw: check if the chip failed to wake up Felix Fietkau
2017-02-02  9:14 ` [PATCH v2 3/3] ath9k: fix race condition in enabling/disabling IRQs Felix Fietkau
2017-02-07  9: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=b4d288b79fd544a58b9571e06e9fa1c0@eusanexr01a.eu.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nbd@nbd.name \
    /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