From: Ping-Ke Shih <pkshih@realtek.com>
To: Kalle Valo <kvalo@kernel.org>
Cc: Kevin Yang <kevin_yang@realtek.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH 0/4] wifi: rtw89: update to follow regulations of China and Thailand
Date: Wed, 27 Sep 2023 07:42:16 +0000 [thread overview]
Message-ID: <fb8ece3e7e44490c93e69654ca404984@realtek.com> (raw)
In-Reply-To: <8734z0842w.fsf@kernel.org>
> -----Original Message-----
> From: Kalle Valo <kvalo@kernel.org>
> Sent: Wednesday, September 27, 2023 3:32 PM
> To: Ping-Ke Shih <pkshih@realtek.com>
> Cc: Kevin Yang <kevin_yang@realtek.com>; linux-wireless@vger.kernel.org
> Subject: Re: [PATCH 0/4] wifi: rtw89: update to follow regulations of China and Thailand
>
> Ping-Ke Shih <pkshih@realtek.com> writes:
>
> > Recently regulations of China and Thailand are changed, and these chips
> > have gotten new certifications, so apply new TX power tables.
> >
> > Zong-Zhe Yang (4):
> > wifi: rtw89: regd: configure Thailand in regulation type
> > wifi: rtw89: 8852c: update TX power tables to R67
> > wifi: rtw89: 8852b: update TX power tables to R35
> > wifi: rtw89: 8851b: update TX power tables to R34
>
> I don't see patch 2 in patchwork but I did receive it to my
> kvalo@kernel.org adddress, maybe it was too big for the list?
Yes, I think so.
I noted that patch 2 was received late from linux-wireless@vger.kernel.org, so
I checked the size and found that was too big. I was trying to split the patch,
but minutes later I received it.
I think I should add a rule to my local script to check if patch size is larger
than 500k to prevent this again.
>
> But I can also apply that manually so no need to split that patch.
>
Thank you.
Ping-Ke
next prev parent reply other threads:[~2023-09-27 7:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 7:21 [PATCH 0/4] wifi: rtw89: update to follow regulations of China and Thailand Ping-Ke Shih
2023-09-27 7:21 ` [PATCH 1/4] wifi: rtw89: regd: configure Thailand in regulation type Ping-Ke Shih
2023-09-27 7:21 ` [PATCH 2/4] wifi: rtw89: 8852c: update TX power tables to R67 Ping-Ke Shih
2023-09-27 7:21 ` [PATCH 3/4] wifi: rtw89: 8852b: update TX power tables to R35 Ping-Ke Shih
2023-09-27 7:21 ` [PATCH 4/4] wifi: rtw89: 8851b: update TX power tables to R34 Ping-Ke Shih
2023-09-27 7:31 ` [PATCH 0/4] wifi: rtw89: update to follow regulations of China and Thailand Kalle Valo
2023-09-27 7:42 ` Ping-Ke Shih [this message]
2023-10-03 11:34 ` 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=fb8ece3e7e44490c93e69654ca404984@realtek.com \
--to=pkshih@realtek.com \
--cc=kevin_yang@realtek.com \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).