From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Tree Davies <tdavies@darkphysics.net>,
gregkh@linuxfoundation.org, dan.carpenter@linaro.org
Cc: linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH] staging: rtl8192e: Rename function HTIOTPeerDetermine to ht_iot_peer_determine
Date: Sun, 25 Jun 2023 16:07:47 +0200 [thread overview]
Message-ID: <ec2fcc62-90b8-f106-958a-7e1eb27009e3@gmail.com> (raw)
In-Reply-To: <ZJdagUiGPqzb5lp+@tacos.darkphysics>
On 6/24/23 23:05, Tree Davies wrote:
> Rename function HTIOTPeerDetermine to ht_iot_peer_determine in order to
> fix checkpatch warning: Avoid CamelCase
>
> Signed-off-by: Tree Davies <tdavies@darkphysics.net>
> ---
> drivers/staging/rtl8192e/rtl819x_HTProc.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/rtl8192e/rtl819x_HTProc.c b/drivers/staging/rtl8192e/rtl819x_HTProc.c
> index f9fa3f2bb728..33fac7d9ada8 100644
> --- a/drivers/staging/rtl8192e/rtl819x_HTProc.c
> +++ b/drivers/staging/rtl8192e/rtl819x_HTProc.c
> @@ -164,7 +164,7 @@ bool IsHTHalfNmodeAPs(struct rtllib_device *ieee)
> return retValue;
> }
>
> -static void HTIOTPeerDetermine(struct rtllib_device *ieee)
> +static void ht_iot_peer_determine(struct rtllib_device *ieee)
> {
> struct rt_hi_throughput *ht_info = ieee->ht_info;
> struct rtllib_network *net = &ieee->current_network;
> @@ -720,7 +720,7 @@ void HTResetSelfAndSavePeerSetting(struct rtllib_device *ieee,
> ht_info->RT2RT_HT_Mode = (enum rt_ht_capability)0;
> }
>
> - HTIOTPeerDetermine(ieee);
> + ht_iot_peer_determine(ieee);
>
> ht_info->iot_action = 0;
> bIOTAction = HTIOTActIsDisableMCS14(ieee, pNetwork->bssid);
Tested-by: Philipp Hortmann <philipp.g.hortmann@gmail.com>
prev parent reply other threads:[~2023-06-25 14:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-24 21:05 [PATCH] staging: rtl8192e: Rename function HTIOTPeerDetermine to ht_iot_peer_determine Tree Davies
2023-06-25 14:07 ` Philipp Hortmann [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=ec2fcc62-90b8-f106-958a-7e1eb27009e3@gmail.com \
--to=philipp.g.hortmann@gmail.com \
--cc=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=tdavies@darkphysics.net \
/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