From: Kalle Valo <kvalo@kernel.org>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: <kevin_yang@realtek.com>, <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 10:31:35 +0300 [thread overview]
Message-ID: <8734z0842w.fsf@kernel.org> (raw)
In-Reply-To: <20230927072156.26336-1-pkshih@realtek.com> (Ping-Ke Shih's message of "Wed, 27 Sep 2023 15:21:52 +0800")
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?
But I can also apply that manually so no need to split that patch.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-09-27 7:31 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 ` Kalle Valo [this message]
2023-09-27 7:42 ` [PATCH 0/4] wifi: rtw89: update to follow regulations of China and Thailand Ping-Ke Shih
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=8734z0842w.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=kevin_yang@realtek.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.