From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 0/9] ath10k: htt rx fixes and clean ups
Date: Fri, 24 Oct 2014 16:30:57 +0300 [thread overview]
Message-ID: <8738adoar2.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1413812438-14640-1-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Mon, 20 Oct 2014 15:40:29 +0200")
Michal Kazior <michal.kazior@tieto.com> writes:
> I've found a couple of issues while reworking rx
> path.
>
>
> Michal Kazior (9):
> ath10k: don't drop control and null func Rx
> ath10k: remove unused variable
> ath10k: use ieee80211 defines for crypto param lengths
> ath10k: fix rx buffer tracing
> ath10k: deduplicate htt rx dma unmapping
> ath10k: don't drop frames aggressively
> ath10k: add extra sanity check when popping amsdu
> ath10k: don't forget to replenish after fragmented Rx
> ath10k: clear htt->rx_confused on load
Thanks, all nine applied.
--
Kalle Valo
prev parent reply other threads:[~2014-10-24 13:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 13:40 [PATCH 0/9] ath10k: htt rx fixes and clean ups Michal Kazior
2014-10-20 13:40 ` [PATCH 1/9] ath10k: don't drop control and null func Rx Michal Kazior
2014-10-20 13:40 ` [PATCH 2/9] ath10k: remove unused variable Michal Kazior
2014-10-20 13:40 ` [PATCH 3/9] ath10k: use ieee80211 defines for crypto param lengths Michal Kazior
2014-10-20 13:40 ` [PATCH 4/9] ath10k: fix rx buffer tracing Michal Kazior
2014-10-20 13:40 ` [PATCH 5/9] ath10k: deduplicate htt rx dma unmapping Michal Kazior
2014-10-20 13:40 ` [PATCH 6/9] ath10k: don't drop frames aggressively Michal Kazior
2014-10-20 13:40 ` [PATCH 7/9] ath10k: add extra sanity check when popping amsdu Michal Kazior
2014-10-23 15:09 ` Kalle Valo
2014-10-20 13:40 ` [PATCH 8/9] ath10k: don't forget to replenish after fragmented Rx Michal Kazior
2014-10-20 13:40 ` [PATCH 9/9] ath10k: clear htt->rx_confused on load Michal Kazior
2014-10-24 13:30 ` 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=8738adoar2.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;
as well as URLs for NNTP newsgroup(s).