Wireless-regdb Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Louis Kotze <loukot@gmail.com>
To: wens@kernel.org
Cc: wireless-regdb@lists.infradead.org, vkosikhin@gmail.com
Subject: Re: [PATCH 3/5] wireless-regdb: Fix 6 GHz LPI power for Russia (RU)
Date: Sat, 18 Apr 2026 22:17:33 +0200	[thread overview]
Message-ID: <20260417070000.ru-v2-plan@gmail.com> (raw)
In-Reply-To: <CAGb2v64R7SCed2FXgL-6w0Qm65Wsvjp-rCr-YHtxQjHWQq2G+Q@mail.gmail.com>

On Thu, 16 Apr 2026 at 16:27, Chen-Yu Tsai <wens@kernel.org> wrote:
> The most restrictive one. Basically we cannot give the user device
> any chance of violating the limits (or any other restrictions).

Understood. Thank you for the clear guidance -- I will apply the same
principle in future audits.

> A full document (such as Valeriy's reply) in the commit log is
> probably too long. Please try to make it more concise. You can also
> provide a link to the other reply on lore.kernel.org to provide more
> context.

Noted. The v2 commit message is shorter and links to the analysis
thread instead of inlining sources.

Valeriy and I have coordinated off-list. He agrees with the
most-restrictive rule for 5150-5350 and is happy for me to send v2
now for the two unambiguous bands. He will follow up separately with
a source-URL update after the lawyer review he mentioned earlier.

v2 summary:
- 5150-5350 MHz: unchanged, stays at 100 mW
- 5650-5850 MHz: 100 mW -> 200 mW
- 5925-6425 MHz: 100 mW -> 200 mW
- References left unchanged in this patch (Valeriy's follow-up will
  replace the eleoscompliance.com/cntd.ru pointers with the SCRF
  primary documents)

v2 sent: https://lore.kernel.org/wireless-regdb/20260418201717.2152301-1-loukot@gmail.com/

Louis


  reply	other threads:[~2026-04-18 20:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAMcSec+mFSUDm+M=0YaNDe26Z2nup2VzzJqz9psxh2-wkT=7Zw@mail.gmail.com>
2026-04-11 22:38 ` Question: Should FCC-region 6 GHz entries use the India PSD methodology? Louis Kotze
2026-04-12  2:34   ` Chen-Yu Tsai
2026-04-16  6:55     ` Louis Kotze
2026-04-16 14:17     ` [PATCH 3/5] wireless-regdb: Fix 6 GHz LPI power for Russia (RU) Louis Kotze
2026-04-16 14:27       ` Chen-Yu Tsai
2026-04-18 20:17         ` Louis Kotze [this message]
2026-04-11 22:21 [PATCH 0/5] wireless-regdb: Fix incorrect entries found during comprehensive audit Louis Kotze
2026-04-11 22:21 ` [PATCH 1/5] wireless-regdb: Update 6 GHz rules for Hong Kong (HK) Louis Kotze
2026-04-13  4:43   ` Chen-Yu Tsai
2026-04-13  4:46     ` Chen-Yu Tsai
2026-04-11 22:21 ` [PATCH 2/5] wireless-regdb: Update 6 GHz rules for South Korea (KR) Louis Kotze
2026-04-13  4:46   ` Chen-Yu Tsai
2026-04-11 22:21 ` [PATCH 3/5] wireless-regdb: Fix 6 GHz LPI power for Russia (RU) Louis Kotze
2026-04-13  5:03   ` Chen-Yu Tsai
2026-04-13  9:32     ` Valeriy Kosikhin
2026-04-11 22:21 ` [PATCH 4/5] wireless-regdb: Remove incorrect DFS flags for Togo (TG) Louis Kotze
2026-04-13  4:56   ` Chen-Yu Tsai
2026-04-16 12:20     ` Louis Kotze
2026-04-11 22:21 ` [PATCH 5/5] wireless-regdb: Fix 60 GHz power unit for Ukraine (UA) Louis Kotze
2026-04-28  6:26 ` (subset) [PATCH 0/5] wireless-regdb: Fix incorrect entries found during comprehensive audit Chen-Yu Tsai

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=20260417070000.ru-v2-plan@gmail.com \
    --to=loukot@gmail.com \
    --cc=vkosikhin@gmail.com \
    --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