From: Kalle Valo <kvalo@codeaurora.org>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: <tony0620emma@gmail.com>, <linux-wireless@vger.kernel.org>,
<timlee@realtek.com>, <kevin_yang@realtek.com>
Subject: Re: [PATCH 2/4] rtw88: add regulatory strategy by chip type
Date: Sun, 29 Aug 2021 14:33:36 +0300 [thread overview]
Message-ID: <87mtp04h9r.fsf@codeaurora.org> (raw)
In-Reply-To: <20210802063140.25670-3-pkshih@realtek.com> (Ping-Ke Shih's message of "Mon, 2 Aug 2021 14:31:38 +0800")
Ping-Ke Shih <pkshih@realtek.com> writes:
> From: Zong-Zhe Yang <kevin_yang@realtek.com>
>
> Realtek chips can program a specific country domain on efuse to
> indicate what is the expected rtw_regulatory. For chips with a
> PGed country domain, we set REGULATORY_STRICT_REG to tell stack
In the commit logs please avoid using acronyms as much as possible, they
make it harder to read. Only after looking at the patch I was able to
figure out that "PGed" means "programmed", or that's I at least assume
it to mean.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2021-08-29 11:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 6:31 [PATCH 0/4] rtw88: update regulartory mapping and adaptivity Ping-Ke Shih
2021-08-02 6:31 ` [PATCH 1/4] rtw88: upgrade rtw_regulatory mechanism and mapping Ping-Ke Shih
2021-08-02 6:31 ` [PATCH 2/4] rtw88: add regulatory strategy by chip type Ping-Ke Shih
2021-08-29 11:33 ` Kalle Valo [this message]
2021-08-30 6:41 ` Pkshih
2021-08-02 6:31 ` [PATCH 3/4] rtw88: support adaptivity for ETSI/JP DFS region Ping-Ke Shih
2021-08-29 11:40 ` Kalle Valo
2021-08-30 6:46 ` Pkshih
2021-09-21 14:47 ` Kalle Valo
2021-08-02 6:31 ` [PATCH 4/4] rtw88: move adaptivity mechanism to firmware Ping-Ke Shih
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=87mtp04h9r.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=kevin_yang@realtek.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=timlee@realtek.com \
--cc=tony0620emma@gmail.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.