From: Ping-Ke Shih <pkshih@realtek.com>
To: "wens@kernel.org" <wens@kernel.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"wireless-regdb@lists.infradead.org"
<wireless-regdb@lists.infradead.org>
Subject: RE: [PATCH v2 4/4] wireless-regdb: Update regulatory info for Mexico (MX) on 6GHz
Date: Wed, 5 Jun 2024 07:44:09 +0000 [thread overview]
Message-ID: <3306967337134439bb7d61e29277ac60@realtek.com> (raw)
In-Reply-To: <20240605071453.8091-4-pkshih@realtek.com>
Ping-Ke Shih <pkshih@realtek.com> wrote:
> diff --git a/db.txt b/db.txt
> index d3b106526252..c4f5e995e422 100644
> --- a/db.txt
> +++ b/db.txt
> @@ -1293,12 +1293,16 @@ country MW: DFS-ETSI
> (5250 - 5330 @ 80), (20), DFS, AUTO-BW
> (5490 - 5710 @ 160), (27), DFS
>
> +# Source:
> +#
> https://www.ift.org.mx/sites/default/files/comunicacion-y-medios/comunicados-ift/comunicado13ift_1.pdf
> +#
> https://www.ift.org.mx/sites/default/files/industria/temasrelevantes/consultaspublicas/documentos/2021
> 0119-cpi6ghz2020-162.pdf
>
Please drop v2. I forgot to correct above links. Sorry for the mistakes.
Ping-Ke
prev parent reply other threads:[~2024-06-05 7:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 7:14 [PATCH v2 1/4] wireless-regdb: Update regulatory info for Malaysia (MY) for 2022 Ping-Ke Shih
2024-06-05 7:14 ` [PATCH v2 2/4] wireless-regdb: Update regulatory info for Morocco (MA) on 6GHz Ping-Ke Shih
2024-06-05 7:14 ` [PATCH v2 3/4] wireless-regdb: Update regulatory info for Chile (CL) " Ping-Ke Shih
2024-06-05 7:14 ` [PATCH v2 4/4] wireless-regdb: Update regulatory info for Mexico (MX) " Ping-Ke Shih
2024-06-05 7:44 ` Ping-Ke Shih [this message]
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=3306967337134439bb7d61e29277ac60@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wens@kernel.org \
--cc=wireless-regdb@lists.infradead.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