From: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: <linux-wireless@vger.kernel.org>, <ath9k-devel@lists.ath9k.org>,
<senthilb@qca.qualcomm.com>, <vthiagar@qca.qualcomm.com>,
<rodrigue@qca.qualcomm.com>,
Rajkumar_contact <rmanohar@qca.qualcomm.com>,
"Manoharan, Sujith" <c_manoha@qca.qualcomm.com>
Subject: Re: [RFC 1/2] ath9k: use ieee80211_free_txskb
Date: Tue, 6 Mar 2012 10:36:21 +0530 [thread overview]
Message-ID: <4F559B4D.5030006@qca.qualcomm.com> (raw)
In-Reply-To: <201203051943.15875.chunkeey@googlemail.com>
>> would you like me to test this patch,
> ? Sure, I would like someone with a AR9300+ to test the patch.
> Currently, I'm stuck with a puny AR9287 [in a router].
> So, I can't run tests all day :(.
>
>> i can just ran a bidirectional traffic test parallel y enabling
>> PAPRD,with this proposed patch.
> Actually, the changes are all within ath9k's tx error paths. So,
> I'm afraid just continuous traffic testing won't do, unless of course
> you can churn out all sorts of tx (dma) errors at the same time.
yes, i can just a start stress test that can run few days in a noisy
channel, with the AR9300 card.
>
> Regards,
> Chr
--
thanks,
shafi
prev parent reply other threads:[~2012-03-06 5:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 16:10 [RFC 1/2] ath9k: use ieee80211_free_txskb Christian Lamparter
2012-02-27 16:32 ` [RFC 2/2] ath9k_htc: " Christian Lamparter
2012-03-01 13:58 ` Mohammed Shafi Shajakhan
2012-03-01 5:39 ` [RFC 1/2] ath9k: " Mohammed Shafi Shajakhan
2012-03-01 11:42 ` Mohammed Shafi Shajakhan
2012-03-01 13:46 ` Mohammed Shafi Shajakhan
2012-03-05 15:00 ` Mohammed Shafi Shajakhan
2012-03-05 15:01 ` Mohammed Shafi Shajakhan
2012-03-05 18:43 ` Christian Lamparter
2012-03-06 5:06 ` Mohammed Shafi Shajakhan [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=4F559B4D.5030006@qca.qualcomm.com \
--to=mohammed@qca.qualcomm.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=c_manoha@qca.qualcomm.com \
--cc=chunkeey@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rmanohar@qca.qualcomm.com \
--cc=rodrigue@qca.qualcomm.com \
--cc=senthilb@qca.qualcomm.com \
--cc=vthiagar@qca.qualcomm.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).