From: Peter Oh <poh@codeaurora.org>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org,
Peter Oh <poh@qca.qualcomm.com>,
Zefir Kurtisi <zefir.kurtisi@neratec.com>
Subject: Re: [PATCH] ath: use PRI value given by spec for fixed PRI
Date: Wed, 15 Apr 2015 10:10:20 -0700 [thread overview]
Message-ID: <552E9B7C.5080109@codeaurora.org> (raw)
In-Reply-To: <87fv817ecp.fsf@kamboji.qca.qualcomm.com>
On 04/15/2015 05:41 AM, Kalle Valo wrote:
> Peter Oh <poh@codeaurora.org> writes:
>
>>> As for your patch at hand, I tested it for ETSI and it does not
>>> change detector performance,
>> The patch is useful when there are many missing pulses within a burst.
>> It happens almost every time when channel loading rate is higher than
>> 40%, but around 30% channel loading does not miss pulses that much.
>>
>>> therefore (please replace 16 with PRI_TOLERANCE in the macro)
>> I'll do.
>>
>>> Acked-by: Zefir Kurtisi <zefir.kurtisi@neratec.com>
> So what's the conclusion? Should I wait for v2 or is this good to
> commit? I didn't quite get Zefir's comment about PRI_TOLERANCE above.
>
Please wait for 2nd patches. I'll prepare the patches that do not void
this current products certificate.
Regards,
Peter
next prev parent reply other threads:[~2015-04-15 17:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 16:59 [PATCH] ath: use PRI value given by spec for fixed PRI Peter Oh
2015-03-30 9:55 ` Zefir Kurtisi
2015-03-30 17:57 ` Peter Oh
2015-04-01 10:04 ` Zefir Kurtisi
2015-04-01 21:00 ` Peter Oh
2015-04-15 12:41 ` Kalle Valo
2015-04-15 17:10 ` Peter Oh [this message]
2015-09-03 18:04 ` Peter Oh
2015-09-04 10:55 ` Zefir Kurtisi
2015-09-04 12:55 ` Kalle Valo
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=552E9B7C.5080109@codeaurora.org \
--to=poh@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=poh@qca.qualcomm.com \
--cc=zefir.kurtisi@neratec.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).