From: Kalle Valo <kvalo@codeaurora.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org,
Yan-Hsuan Chuang <yhchuang@realtek.com>,
Pkshih <pkshih@realtek.com>, Birming Chiu <birming@realtek.com>,
Shaofu <shaofu@realtek.com>, Steven Ting <steventing@realtek.com>
Subject: Re: [PATCH 00/14] rtlwifi: btcoex: Second set of changes for rtl8821ae 2ant
Date: Thu, 20 Apr 2017 07:59:18 +0300 [thread overview]
Message-ID: <87zifb65eh.fsf@codeaurora.org> (raw)
In-Reply-To: <20170415203200.22979-1-Larry.Finger@lwfinger.net> (Larry Finger's message of "Sat, 15 Apr 2017 15:31:46 -0500")
Larry Finger <Larry.Finger@lwfinger.net> writes:
> These patches are the second set of patches for file
> btcoexist/halbtc8821a2ant.c.
>
> Signed-off-by: Yan-Hsuan Chuang <yhchuang@realtek.com>
> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
> Cc: Pkshih <pkshih@realtek.com>
> Cc: Birming Chiu <birming@realtek.com>
> Cc: Shaofu <shaofu@realtek.com>
> Cc: Steven Ting <steventing@realtek.com>
BTW, please try to limit the amount of patches you send. I haven't
counted how many rtlwifi patches there are from the last week but it's
just too much, even if they are in smaller sets like this one. Reviewing
them is just too tedious when you see that you have something like 50
more still to go.
If you send two sets with reasonable size[1] per week I don't have any
problems. But if you send five such sets per week I will get annoyed :)
So try to strect the submission a bit to stay below ~30 patches per week
limit, please.
So I'm not sure if I'm able to apply all of pending rtlwifi patches
before the merge window opens, but I'll try.
[1] a reasonable size is around a dozen patches per set
--
Kalle Valo
next prev parent reply other threads:[~2017-04-20 4:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-15 20:31 [PATCH 00/14] rtlwifi: btcoex: Second set of changes for rtl8821ae 2ant Larry Finger
2017-04-15 20:31 ` [PATCH 01/14] rtlwifi: btcoex: 21a 2ant: turn on sw dac swing and check if is sco_only Larry Finger
2017-04-20 7:26 ` [01/14] " Kalle Valo
2017-04-15 20:31 ` [PATCH 02/14] rtlwifi: btcoex: 21a 2ant: add threshold to examine bt rssi Larry Finger
2017-04-15 20:31 ` [PATCH 03/14] rtlwifi: btcoex: 21a 2ant: force wifi to use RF path A Larry Finger
2017-04-15 20:31 ` [PATCH 04/14] rtlwifi: btcoex: 21a 2ant: more combinations of wifi/bt rssi state Larry Finger
2017-04-15 20:31 ` [PATCH 05/14] rtlwifi: btcoex: 21a 2ant: fix some coding style issues Larry Finger
2017-04-15 20:31 ` [PATCH 06/14] rtlwifi: btcoex: 21a 2ant: set tdma based on rssi state amd limit rx agg size Larry Finger
2017-04-15 20:31 ` [PATCH 07/14] rtlwifi: btcoex: 21a 2ant: add multiport action for p2p/miracast Larry Finger
2017-04-15 20:31 ` [PATCH 08/14] rtlwifi: btcoex: 21a 2ant: monitor extra wifi rssi to examine network status Larry Finger
2017-04-15 20:31 ` [PATCH 09/14] rtlwifi: btcoex: 21a 2ant: notify fw the number of APs Larry Finger
2017-04-15 20:31 ` [PATCH 10/14] rtlwifi: btcoex: 21a 2ant: dec bt power according to bt rssi and set tdma Larry Finger
2017-04-15 20:31 ` [PATCH 11/14] rtlwifi: btcoex: 21a 2ant: macro for bt rssi threshold Larry Finger
2017-04-15 20:31 ` [PATCH 12/14] rtlwifi: btcoex: 21a 2ant: do not limit rx agg size Larry Finger
2017-04-15 20:31 ` [PATCH 13/14] rtlwifi: btcoex: 21a 2ant: just return when wifi is under ips Larry Finger
2017-04-15 20:32 ` [PATCH 14/14] rtlwifi: btcoex: 21a 2ant: wifi is linking action Larry Finger
2017-04-20 4:59 ` Kalle Valo [this message]
2017-04-20 18:54 ` [PATCH 00/14] rtlwifi: btcoex: Second set of changes for rtl8821ae 2ant Larry Finger
2017-04-21 6:55 ` Kalle Valo
2017-04-21 14:40 ` Larry Finger
2017-04-24 11:26 ` 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=87zifb65eh.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=Larry.Finger@lwfinger.net \
--cc=birming@realtek.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=shaofu@realtek.com \
--cc=steventing@realtek.com \
--cc=yhchuang@realtek.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).