From: Kalle Valo <kvalo@codeaurora.org>
To: <yhchuang@realtek.com>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 01/11] rtw88: resolve order of tx power setting routines
Date: Thu, 27 Jun 2019 17:27:41 +0000 (UTC) [thread overview]
Message-ID: <20190627172741.21EE260A05@smtp.codeaurora.org> (raw)
In-Reply-To: <1559116487-5244-2-git-send-email-yhchuang@realtek.com>
<yhchuang@realtek.com> wrote:
> From: Yan-Hsuan Chuang <yhchuang@realtek.com>
>
> Some functions that should be static are unnecessarily exposed, remove
> their declaration in header file phy.h.
>
> After resolving their declaration order, they can be declared as static.
> So this commit changes nothing except the order and marking them static.
>
> Signed-off-by: Yan-Hsuan Chuang <yhchuang@realtek.com>
10 patches applied to wireless-drivers-next.git, thanks.
fa6dfe6bff24 rtw88: resolve order of tx power setting routines
226746fd1201 rtw88: do not use (void *) as argument
43712199e05b rtw88: unify prefixes for tx power setting routine
522801493e7b rtw88: remove unused variable
764038160aea rtw88: fix incorrect tx power limit at 5G
adf3c676d1d2 rtw88: choose the lowest as world-wide power limit
93f68a865f11 rtw88: correct power limit selection
191c4257ba19 rtw88: update tx power limit table to RF v20
0d350f0a91f2 rtw88: remove all RTW_MAX_POWER_INDEX macro
b741422218ef rtw88: refine flow to get tx power index
--
https://patchwork.kernel.org/patch/10966415/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2019-06-27 17:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 7:54 [PATCH 00/11] rtw88: power index setting routine updates and fixes yhchuang
2019-05-29 7:54 ` [PATCH 01/11] rtw88: resolve order of tx power setting routines yhchuang
2019-05-29 15:16 ` Larry Finger
2019-05-30 2:29 ` Tony Chuang
2019-05-30 2:57 ` Larry Finger
2019-05-30 4:59 ` Kalle Valo
2019-05-30 5:05 ` Tony Chuang
2019-05-30 5:11 ` Kalle Valo
2019-05-30 5:15 ` Tony Chuang
2019-06-27 17:27 ` Kalle Valo [this message]
2019-05-29 7:54 ` [PATCH 02/11] rtw88: do not use (void *) as argument yhchuang
2019-05-29 7:54 ` [PATCH 03/11] rtw88: unify prefixes for tx power setting routine yhchuang
2019-05-29 7:54 ` [PATCH 04/11] rtw88: remove unused variable yhchuang
2019-05-29 7:54 ` [PATCH 05/11] rtw88: fix incorrect tx power limit at 5G yhchuang
2019-05-29 7:54 ` [PATCH 06/11] rtw88: choose the lowest as world-wide power limit yhchuang
2019-05-29 7:54 ` [PATCH 07/11] rtw88: correct power limit selection yhchuang
2019-05-29 7:54 ` [PATCH 08/11] rtw88: update tx power limit table to RF v20 yhchuang
2019-05-29 7:54 ` [PATCH 09/11] rtw88: remove all RTW_MAX_POWER_INDEX macro yhchuang
2019-07-11 22:05 ` Brian Norris
2019-07-16 8:15 ` Tony Chuang
2019-05-29 7:54 ` [PATCH 10/11] rtw88: refine flow to get tx power index yhchuang
2019-05-29 7:54 ` [PATCH 11/11] rtw88: debug: dump tx power indexes in use yhchuang
2019-06-01 22:51 ` Joe Perches
2019-06-04 8:18 ` Tony Chuang
2019-06-11 10:07 ` [PATCH 00/11] rtw88: power index setting routine updates and fixes Tony Chuang
2019-06-11 13:39 ` Kalle Valo
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=20190627172741.21EE260A05@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).