On Thu, 2021-01-14 at 07:21 +0000, Kalle Valo wrote: > Ping-Ke Shih <pkshih@xxxxxxxxxxx> 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. > Sorry for the mess. I'll follow your guides for further submission. To avoid frequently submitting patches results from exceeding patch size limit. I'd like to know the patch size limit accepted by patchwork. As I know, the limit is about 512k, so it is expected that below patches don't appear in patchwork 1. patch 5/5 of v1 (978K) 2. patch 6/7 of v2 (532K) But, I don't know why the table file (patch 16/18) of rtw89 whose size is 772k can appear in patchwork. Does patchwork have different limits of existing and new file? Moreover, if new file exceeds the limit someday, how can I deal with it? Can I split the new file into two or more patches? --- Ping-Ke
