From: Kalle Valo <kvalo@codeaurora.org>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: <tony0620emma@gmail.com>, <linux-wireless@vger.kernel.org>,
<phhuang@realtek.com>
Subject: Re: [PATCH RESEND v3 0/8] rtw88: improve TX performance in field
Date: Thu, 14 Jan 2021 09:21:57 +0200 [thread overview]
Message-ID: <874kjkrnje.fsf@codeaurora.org> (raw)
In-Reply-To: <20210114010950.3316-1-pkshih@realtek.com> (Ping-Ke Shih's message of "Thu, 14 Jan 2021 09:09:42 +0800")
Ping-Ke Shih <pkshih@realtek.com> writes:
> Improve TX performance in aspects of protocol and software design. Also,
> update PHY parameters to fix incorrect RSSI report.
>
> v2: Since 5/5 of v1 is too large, I split it into three patches.
> v3: Since 6/7 of v2 is still too large for patchwork, I split parameter
> into four patches.
>
> ---
> RESEND v3 due to no appearance of patchwork
Please avoid using "RESEND", instead just increase the version (in this
case you should have used v4). Makes my sorting easier and it's not like
we are running out of numbers for versions :)
And mailing lists and patchwork can be slow sometimes (recently more
often), so please wait at least 12h before resubmitting any patches. Now
both v3 and "v3 RESEND" are in patchwork.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2021-01-14 7:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 1:09 [PATCH RESEND v3 0/8] rtw88: improve TX performance in field Ping-Ke Shih
2021-01-14 1:09 ` [PATCH RESEND v3 1/8] rtw88: add dynamic rrsr configuration Ping-Ke Shih
2021-01-14 1:09 ` [PATCH RESEND v3 2/8] rtw88: add rts condition Ping-Ke Shih
2021-01-14 1:09 ` [PATCH RESEND v3 3/8] rtw88: add napi support Ping-Ke Shih
2021-01-14 1:09 ` [PATCH RESEND v3 4/8] rtw88: replace tx tasklet with tx work Ping-Ke Shih
2021-01-14 18:34 ` Brian Norris
2021-01-14 18:41 ` Kalle Valo
2021-01-14 1:09 ` [PATCH RESEND v3 5/8] rtw88: 8822c: update MAC/BB parameter tables to v60 Ping-Ke Shih
2021-01-14 1:09 ` [PATCH RESEND v3 6/8] rtw88: 8822c: update RF_A " Ping-Ke Shih
2021-01-14 1:09 ` [PATCH RESEND v3 7/8] rtw88: 8822c: update RF_B (1/2) " Ping-Ke Shih
2021-01-14 1:09 ` [PATCH RESEND v3 8/8] rtw88: 8822c: update RF_B (2/2) " Ping-Ke Shih
2021-01-14 7:21 ` Kalle Valo [this message]
2021-01-15 1:17 ` [PATCH RESEND v3 0/8] rtw88: improve TX performance in field Pkshih
2021-01-15 7:52 ` Kalle Valo
2021-01-15 8:07 ` Pkshih
2021-01-18 14:44 ` Kalle Valo
2021-01-19 2:15 ` Pkshih
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=874kjkrnje.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=phhuang@realtek.com \
--cc=pkshih@realtek.com \
--cc=tony0620emma@gmail.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).