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 0/6] ath10k: random fixes 2015-07-09
Date: Sat, 11 Jul 2015 19:17:34 +0300 [thread overview]
Message-ID: <87a8v2wtwh.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1436440119-30231-1-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Thu, 9 Jul 2015 13:08:33 +0200")
Michal Kazior <michal.kazior@tieto.com> writes:
> I've done most of the patches while testing P2P
> but they aren't limited to that scope.
>
> There are no inter-dependencies within the patchset
> so single patches should be easily cherry-pickable
> in case, e.g. some patches raise concerns or are
> decided to be dropped during review.
>
>
> Michal Kazior (6):
> ath10k: don't set cck/ofdm scan flags
> ath10k: limit multi-vif ps more aggresivelly
> ath10k: fix hw roc expiration notifcation
> ath10k: update vdev ps state on start
> ath10k: fix per-vif queue locking
> ath10k: tweak interface combinations
Thanks, all six applied.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2015-07-11 16:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 11:08 [PATCH 0/6] ath10k: random fixes 2015-07-09 Michal Kazior
2015-07-09 11:08 ` [PATCH 1/6] ath10k: don't set cck/ofdm scan flags Michal Kazior
2015-07-09 11:08 ` [PATCH 2/6] ath10k: limit multi-vif ps more aggresivelly Michal Kazior
2015-07-09 11:08 ` [PATCH 3/6] ath10k: fix hw roc expiration notifcation Michal Kazior
2015-07-09 11:08 ` [PATCH 4/6] ath10k: update vdev ps state on start Michal Kazior
2015-07-09 11:08 ` [PATCH 5/6] ath10k: fix per-vif queue locking Michal Kazior
2015-07-09 11:08 ` [PATCH 6/6] ath10k: tweak interface combinations Michal Kazior
2015-07-11 16:17 ` 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=87a8v2wtwh.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