From: Kalle Valo <kvalo@codeaurora.org>
To: <tehuang@realtek.com>
Cc: <yhchuang@realtek.com>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 5/5] rtw88: show current regulatory in tx power table
Date: Fri, 25 Sep 2020 19:29:14 +0300 [thread overview]
Message-ID: <87mu1dg6qt.fsf@codeaurora.org> (raw)
In-Reply-To: <20200925061219.23754-6-tehuang@realtek.com> (tehuang@realtek.com's message of "Fri, 25 Sep 2020 14:12:19 +0800")
<tehuang@realtek.com> writes:
> From: Tzu-En Huang <tehuang@realtek.com>
>
> In the transmit power table, it is important to know what the regulatory
> currently is. For different regulatories, there are different
> transmit power limits. Show which regulatory the driver is currently
> using.
>
> Change-Id: Id92aa6a833053fbf0b065c9ff946d7d4722897fd
No Change-Id tags, but I can remove it during commit. No need to resend
just because of this.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2020-09-25 16:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 6:12 [PATCH 0/5] rtw88: add firmware crash recovery and some fixes tehuang
2020-09-25 6:12 ` [PATCH 1/5] rtw88: increse the size of rx buffer size tehuang
2020-09-29 8:23 ` Kalle Valo
2020-09-25 6:12 ` [PATCH 2/5] rtw88: handle and recover when firmware crash tehuang
2020-09-29 8:20 ` Kalle Valo
2020-09-25 6:12 ` [PATCH 3/5] rtw88: add dump firmware fifo support tehuang
2020-10-01 19:06 ` Nathan Chancellor
2020-10-02 8:14 ` Kalle Valo
2020-10-02 8:43 ` Nathan Chancellor
2020-10-06 5:53 ` Kalle Valo
2020-09-25 6:12 ` [PATCH 4/5] rtw88: add dump fw crash log tehuang
2020-09-25 6:12 ` [PATCH 5/5] rtw88: show current regulatory in tx power table tehuang
2020-09-25 16:29 ` Kalle Valo [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=87mu1dg6qt.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tehuang@realtek.com \
--cc=yhchuang@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.