All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH 0/7] ath10k: htt rx fixes
Date: Tue, 30 Apr 2013 11:01:07 +0300	[thread overview]
Message-ID: <87ip34la64.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1366965448-8390-1-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Fri, 26 Apr 2013 10:37:21 +0200")

Michal Kazior <michal.kazior@tieto.com> writes:

> This patchset addresses issues with fragmented
> (802.11b) frames.
>
> Michal Kazior (7):
>   ath10k: zero htt_rx_info struct in frag rx handler
>   ath10k: do not pop more than one frame in frag rx handler
>   ath10k: add safety check after popping a frame in frag rx
>   ath10k: move ath10k_htt_rx_free_msdu_chain()
>   ath10k: drop all msdus in case of htt rx failure
>   ath10k: fix tkip fragment rx
>   ath10k: strip protected flag

Thanks, all seven applied.

-- 
Kalle Valo

      parent reply	other threads:[~2013-04-30  8:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-26  8:37 [ath9k-devel] [PATCH 0/7] ath10k: htt rx fixes Michal Kazior
2013-04-26  8:37 ` [ath9k-devel] [PATCH 1/7] ath10k: zero htt_rx_info struct in frag rx handler Michal Kazior
2013-04-26  8:37 ` [ath9k-devel] [PATCH 2/7] ath10k: do not pop more than one frame " Michal Kazior
2013-04-26  8:37 ` [ath9k-devel] [PATCH 3/7] ath10k: add safety check after popping a frame in frag rx Michal Kazior
2013-04-26  8:37 ` [ath9k-devel] [PATCH 4/7] ath10k: move ath10k_htt_rx_free_msdu_chain() Michal Kazior
2013-04-26  8:37 ` [ath9k-devel] [PATCH 5/7] ath10k: drop all msdus in case of htt rx failure Michal Kazior
2013-04-26  8:37 ` [ath9k-devel] [PATCH 6/7] ath10k: fix tkip fragment rx Michal Kazior
2013-04-26  8:37 ` [ath9k-devel] [PATCH 7/7] ath10k: strip protected flag Michal Kazior
2013-04-30  7:58   ` Kalle Valo
2013-04-30  8:07     ` Michal Kazior
2013-04-30  8:20       ` Kalle Valo
2013-04-30  8: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=87ip34la64.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath9k-devel@lists.ath9k.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.