From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Sujith Manoharan <sujith@msujith.org>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH] ath10k: Make HTT fill size configurable
Date: Thu, 15 Jan 2015 10:35:02 +0200 [thread overview]
Message-ID: <87iog8zbk9.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <21687.30881.260644.741211@gargle.gargle.HOWL> (Sujith Manoharan's message of "Thu, 15 Jan 2015 13:51:53 +0530")
Sujith Manoharan <sujith@msujith.org> writes:
> Sujith Manoharan wrote:
>> None. The default stays the same. But, it can be adjusted based
>> on the platform, if higher throughput is desired.
>
> But, anyway, this patch can be dropped. We'll change the fill level
> restriction internally, based on the customer's platform.
I'm sad to hear that, now others cannot benefit from your work.
What was wrong with my proposal? Would it help if I write an RFC patch?
Just tell me what HTT fill value I should use.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2015-01-15 8:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 4:39 [PATCH] ath10k: Make HTT fill size configurable Sujith Manoharan
2015-01-07 10:14 ` Michal Kazior
2015-01-07 10:37 ` Sujith Manoharan
2015-01-13 14:44 ` Kalle Valo
2015-01-13 20:56 ` Sujith Manoharan
2015-01-07 10:53 ` Vasanthakumar Thiagarajan
2015-01-13 14:48 ` Kalle Valo
2015-01-13 15:03 ` Kalle Valo
2015-01-13 21:08 ` Sujith Manoharan
2015-01-14 9:22 ` Michal Kazior
2015-01-14 9:50 ` Sujith Manoharan
2015-01-14 10:12 ` Michal Kazior
2015-01-15 0:17 ` Sujith Manoharan
2015-01-15 7:19 ` Kalle Valo
2015-01-15 7:38 ` Kalle Valo
2015-01-15 7:50 ` Sujith Manoharan
2015-01-15 8:09 ` Kalle Valo
2015-01-15 8:16 ` Sujith Manoharan
2015-01-15 8:21 ` Sujith Manoharan
2015-01-15 8:35 ` Kalle Valo [this message]
2015-01-15 8:47 ` Sujith Manoharan
2015-01-15 8:32 ` Kalle Valo
2015-01-15 8:43 ` Sujith Manoharan
2015-01-15 23:03 ` Julian Calaby
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=87iog8zbk9.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sujith@msujith.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