From: Ilya K <me@0upti.me>
To: Louis Kotze <loukot@gmail.com>
Cc: Chen-Yu Tsai <wens@kernel.org>,
Valeriy Kosikhin <vkosikhin@gmail.com>,
wireless-regdb@lists.infradead.org,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] wireless-regdb: allow 320MHz channel width for Russia
Date: Tue, 28 Apr 2026 11:16:38 +0300 [thread overview]
Message-ID: <b9d9d6e1-91c4-487f-82af-e53d4148c11b@0upti.me> (raw)
In-Reply-To: <20260428074500.ru-320-review-resend@gmail.com>
On 2026-04-28 10:44, Louis Kotze wrote:
>
> Note that the patch base predates the recent RU power update (commit
> 6873bfe in wens/wireless-regdb), which changed 5925-6425 from 100 mW
> to 200 mW, so this needs a rebase on current HEAD before it can be
> applied.
>
I can resend a rebased version if necessary.
next prev parent reply other threads:[~2026-04-28 8:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 11:00 [PATCH] wireless-regdb: allow 320MHz channel width for Russia K900
2026-04-28 7:44 ` Louis Kotze
2026-04-28 8:16 ` Ilya K [this message]
2026-04-28 9:23 ` 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=b9d9d6e1-91c4-487f-82af-e53d4148c11b@0upti.me \
--to=me@0upti.me \
--cc=linux-wireless@vger.kernel.org \
--cc=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