From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Gary Rookard <garyrookard@fastmail.org>, gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 5/5] staging: rtl8192e: renamed variable HTIOTActIsMgntUseCCK6M
Date: Thu, 23 Nov 2023 22:05:34 +0100 [thread overview]
Message-ID: <4df855f1-77e9-44a2-a024-aa5c7d661642@gmail.com> (raw)
In-Reply-To: <20231123144337.13112-6-garyrookard@fastmail.org>
On 11/23/23 15:43, Gary Rookard wrote:
> Renamed from Pascal/CamelCase to Snake case the variable
> HTIOTActIsMgntUseCCK6M.
> HTIOTActIsMgntUseCCK6M -> ht_iot_act_is_mgnt_use_cck_6m
>
> Linux kernel coding style (cleanup), checkpatch Avoid CamelCase.
> Driver/module rtl8192e compiles.
>
> Signed-off-by: Gary Rookard <garyrookard@fastmail.org>
> ---
> v3: Corrected versioning fron v1 -> v3, includes change history.
> v2: v2 was Skipped over..v3 corrects this.
> v1: Style and compile issues, asked to redo.
>
> 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 0873c19ca051..f43249fd78d7 100644
> --- a/drivers/staging/rtl8192e/rtl819x_HTProc.c
> +++ b/drivers/staging/rtl8192e/rtl819x_HTProc.c
> @@ -207,7 +207,7 @@ static void ht_iot_peer_determine(struct rtllib_device *ieee)
> netdev_dbg(ieee->dev, "IOTPEER: %x\n", ht_info->IOTPeer);
> }
>
> -static u8 HTIOTActIsMgntUseCCK6M(struct rtllib_device *ieee,
> +static u8 ht_iot_act_is_mgnt_use_cck_6m(struct rtllib_device *ieee,
> struct rtllib_network *network)
CHECK: Alignment should match open parenthesis
#33: FILE: drivers/staging/rtl8192e/rtl819x_HTProc.c:211:
+static u8 ht_iot_act_is_mgnt_use_cck_6m(struct rtllib_device *ieee,
struct rtllib_network *network)
Please use checkpatch on your patches. Alignment issues can be fixed up
by you. CamelCase oft not when the variable did not change within your
patch.
> {
> u8 retValue = 0;
> @@ -675,7 +675,7 @@ void HTResetSelfAndSavePeerSetting(struct rtllib_device *ieee,
> ht_iot_peer_determine(ieee);
>
> ht_info->iot_action = 0;
> - bIOTAction = HTIOTActIsMgntUseCCK6M(ieee, pNetwork);
> + bIOTAction = ht_iot_act_is_mgnt_use_cck_6m(ieee, pNetwork);
> if (bIOTAction)
> ht_info->iot_action |= HT_IOT_ACT_MGNT_USE_CCK_6M;
> bIOTAction = HTIOTActIsCCDFsync(ieee);
next prev parent reply other threads:[~2023-11-23 21:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 14:43 [PATCH v3 0/5] staging: rtl8192e: renaming 5 different variables patch series Gary Rookard
2023-11-23 14:43 ` [PATCH v3 1/5] staging: rtl8192e: renamed variable HTMcsToDataRate Gary Rookard
2023-11-23 14:43 ` [PATCH v3 2/5] staging: rtl8192e: renamed variable TXCountToDataRate Gary Rookard
2023-11-23 20:56 ` Philipp Hortmann
2023-11-23 23:19 ` Gary Rookard
2023-11-24 11:30 ` Greg KH
2023-11-23 14:43 ` [PATCH v3 3/5] staging: rtl8192e: renamed variable IsHTHalfNmodeAPs Gary Rookard
2023-11-23 14:43 ` [PATCH v3 4/5] staging: rtl8192e: renamed variable HTIOTPeerDetermine Gary Rookard
2023-11-23 14:43 ` [PATCH v3 5/5] staging: rtl8192e: renamed variable HTIOTActIsMgntUseCCK6M Gary Rookard
2023-11-23 21:05 ` Philipp Hortmann [this message]
2023-11-23 21:11 ` [PATCH v3 0/5] staging: rtl8192e: renaming 5 different variables patch series Philipp Hortmann
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=4df855f1-77e9-44a2-a024-aa5c7d661642@gmail.com \
--to=philipp.g.hortmann@gmail.com \
--cc=garyrookard@fastmail.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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