From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH v2 0/2] ath10k: fix radar/cac
Date: Fri, 11 Apr 2014 08:25:20 +0300 [thread overview]
Message-ID: <87bnw8h1z3.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1396610926-5787-1-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Fri, 4 Apr 2014 13:28:44 +0200")
Michal Kazior <michal.kazior@tieto.com> writes:
> Hi,
>
> This loosely depends on `ath10k: refactor monitor
> code`. Without it patch this patchset introduces
> some (harmless) runtime warnings.
>
> This v2 introduces a non-functional patch to avoid
> forward declaration. The [1/2] has a little
> conflict with `ath10k: refactor monitor code`
> which renames ath10k_monitor_stop() to
> ath10k_monitor_vdev_stop().
>
> Part of the original CAC problem is also addressed
> in `mac80211: fix radar_enabled propagation`.
>
>
> Michal Kazior (2):
> ath10k: reorder functions
> ath10k: refactor radar detection code
Thanks, both patches applied.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2014-04-11 5:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1396015934-7723-1-git-send-email-michal.kazior@tieto.com>
2014-04-01 7:25 ` [PATCH] ath10k: fix initial radar detection logic Michal Kazior
2014-04-02 5:27 ` Kalle Valo
2014-04-02 5:48 ` Michal Kazior
2014-04-04 11:28 ` [PATCH v2 0/2] ath10k: fix radar/cac Michal Kazior
2014-04-04 11:28 ` [PATCH v2 1/2] ath10k: reorder functions Michal Kazior
2014-04-07 13:52 ` Kalle Valo
2014-04-08 6:07 ` Michal Kazior
2014-04-04 11:28 ` [PATCH v2 2/2] ath10k: refactor radar detection code Michal Kazior
2014-04-07 14:04 ` Kalle Valo
2014-04-08 6:32 ` Michal Kazior
2014-04-08 7:04 ` Kalle Valo
2014-04-11 5:25 ` 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=87bnw8h1z3.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.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