From: Kalle Valo <kvalo@qca.qualcomm.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH 0/4] ath10k: fixes
Date: Fri, 7 Jun 2013 10:17:09 +0300 [thread overview]
Message-ID: <871u8ewft6.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20912.29720.449222.694682@gargle.gargle.HOWL> (Sujith Manoharan's message of "Thu, 6 Jun 2013 17:05:52 +0530")
Sujith Manoharan <sujith@msujith.org> writes:
> Michal Kazior wrote:
>> This is part 1 of 4 of a bigger patchset.
>> Split for easier review.
>>
>> Contains functional fixes.
>>
>> Michal Kazior (4):
>> ath10k: fix teardown ordering
>> ath10k: fix possible deadlock
>> ath10k: setup rts/frag thresholds upon vdev creation
>> ath10k: do not setup rts/frag thresholds for suspended interfaces
>>
>> drivers/net/wireless/ath/ath10k/mac.c | 30 +++++++++++++++++++++++++-----
>> drivers/net/wireless/ath/ath10k/pci.c | 2 +-
>> 2 files changed, 26 insertions(+), 6 deletions(-)
Thanks, applied.
> Other than the observation about an incomplete FW feature,
> this looks good to me.
I applied that patch anyway as I'm hoping it will be implemented in fw
eventually. Thanks for the review.
--
Kalle Valo
prev parent reply other threads:[~2013-06-07 7:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 10:23 [ath9k-devel] [PATCH 0/4] ath10k: fixes Michal Kazior
2013-06-06 10:23 ` [ath9k-devel] [PATCH 1/4] ath10k: fix teardown ordering Michal Kazior
2013-06-06 10:23 ` [ath9k-devel] [PATCH 2/4] ath10k: fix possible deadlock Michal Kazior
2013-06-06 10:23 ` [ath9k-devel] [PATCH 3/4] ath10k: setup rts/frag thresholds upon vdev creation Michal Kazior
2013-06-06 11:33 ` Sujith Manoharan
2013-06-06 10:23 ` [ath9k-devel] [PATCH 4/4] ath10k: do not setup rts/frag thresholds for suspended interfaces Michal Kazior
2013-06-06 11:35 ` [ath9k-devel] [PATCH 0/4] ath10k: fixes Sujith Manoharan
2013-06-07 7: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=871u8ewft6.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox