Linux kernel staging patches
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@inria.fr>
To: Mahak Gupta <mahak_g@cs.iitr.ac.in>
Cc: Larry.Finger@lwfinger.net, florian.c.schilhabel@googlemail.com,
	 gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
	 linux-kernel@vger.kernel.org, outreachy@lists.linux.dev
Subject: Re: [PATCH] staging: rtl8712: fix camel case in function r8712_generate_ie
Date: Thu, 7 Apr 2022 14:14:29 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2204071414080.2213@hadrien> (raw)
In-Reply-To: <20220407120945.31030-1-mahak_g@cs.iitr.ac.in>



On Thu, 7 Apr 2022, Mahak Gupta wrote:

> Adhere to linux kernel coding style.
>
> Reported by checkpatch:
>
> CHECK: Avoid CamelCase: <beaconPeriod>

As another patch, you could also adjust the structure field name.

julia

>
> Signed-off-by: Mahak Gupta <mahak_g@cs.iitr.ac.in>
> ---
>  drivers/staging/rtl8712/ieee80211.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/rtl8712/ieee80211.c b/drivers/staging/rtl8712/ieee80211.c
> index f926809b1021..7d8f1a29d18a 100644
> --- a/drivers/staging/rtl8712/ieee80211.c
> +++ b/drivers/staging/rtl8712/ieee80211.c
> @@ -162,13 +162,13 @@ int r8712_generate_ie(struct registry_priv *registrypriv)
>  	uint sz = 0;
>  	struct wlan_bssid_ex *dev_network = &registrypriv->dev_network;
>  	u8 *ie = dev_network->IEs;
> -	u16 beaconPeriod = (u16)dev_network->Configuration.BeaconPeriod;
> +	u16 beacon_period = (u16)dev_network->Configuration.BeaconPeriod;
>
>  	/*timestamp will be inserted by hardware*/
>  	sz += 8;
>  	ie += sz;
>  	/*beacon interval : 2bytes*/
> -	*(__le16 *)ie = cpu_to_le16(beaconPeriod);
> +	*(__le16 *)ie = cpu_to_le16(beacon_period);
>  	sz += 2;
>  	ie += 2;
>  	/*capability info*/
> --
> 2.17.1
>
>
>

  reply	other threads:[~2022-04-07 12:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-07 12:09 [PATCH] staging: rtl8712: fix camel case in function r8712_generate_ie Mahak Gupta
2022-04-07 12:14 ` Julia Lawall [this message]
2022-04-07 16:17   ` MAHAK GUPTA
2022-04-07 17:58     ` Julia Lawall

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=alpine.DEB.2.22.394.2204071414080.2213@hadrien \
    --to=julia.lawall@inria.fr \
    --cc=Larry.Finger@lwfinger.net \
    --cc=florian.c.schilhabel@googlemail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=mahak_g@cs.iitr.ac.in \
    --cc=outreachy@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