All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@inria.fr>
To: Briana Oursler <briana.oursler@gmail.com>
Cc: gregkh@linuxfoundation.org, forest@alittletooquiet.net,
	 outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [Outreachy][PATCH] staging: vt6655: Replace camel case variable names.
Date: Thu, 26 Mar 2020 08:17:58 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.21.2003260814590.3019@hadrien> (raw)
In-Reply-To: <20200326012850.94416-1-briana.oursler@gmail.com>



On Wed, 25 Mar 2020, Briana Oursler wrote:

> Replaces camel case variable names with snake case in baseband.h and
> dependencies.
>
> Signed-off-by: Briana Oursler <briana.oursler@gmail.com>
> ---
>  drivers/staging/vt6655/baseband.c    | 317 ++++++++++++++-------------
>  drivers/staging/vt6655/baseband.h    |  38 ++--
>  drivers/staging/vt6655/card.c        |  48 ++--
>  drivers/staging/vt6655/channel.c     |   4 +-
>  drivers/staging/vt6655/device_main.c |  20 +-
>  drivers/staging/vt6655/rf.c          |   4 +-
>  drivers/staging/vt6655/rxtx.c        |  62 +++---
>  7 files changed, 255 insertions(+), 238 deletions(-)
>
> diff --git a/drivers/staging/vt6655/baseband.c b/drivers/staging/vt6655/baseband.c
> index b4cdc0b7fee7..9909b9d51f7a 100644
> --- a/drivers/staging/vt6655/baseband.c
> +++ b/drivers/staging/vt6655/baseband.c
> @@ -12,12 +12,12 @@
>   * Date: Aug.22, 2002
>   *
>   * Functions:
> - *      BBuGetFrameTime        - Calculate data frame transmitting time
> + *      bb_u_get_frame_time        - Calculate data frame transmitting time
>   *      BBvCalculateParameter   - Calculate PhyLength, PhyService and Phy Signal
>   *                               parameter for baseband Tx
> - *      BBbReadEmbedded         - Embedded read baseband register via MAC
> - *      BBbWriteEmbedded        - Embedded write baseband register via MAC
> - *      BBbVT3253Init          - VIA VT3253 baseband chip init code
> + *      bb_b_read_embedded         - Embedded read baseband register via MAC
> + *      bb_b_write_embedded        - Embedded write baseband register via MAC
> + *      bb_b_vt3253_init          - VIA VT3253 baseband chip init code

The comments about the meaning of the variables should remain lines up.

[...]

> -	unsigned int uFrameTime;
> -	unsigned int uPreamble;
> -	unsigned int uTmp;
> -	unsigned int uRateIdx = (unsigned int)wRate;
> -	unsigned int uRate = 0;
> +	unsigned int u_frame_time;
> +	unsigned int u_preamble;
> +	unsigned int u_tmp;
> +	unsigned int u_rate_idx = (unsigned int)w_rate;
> +	unsigned int u_rate = 0;

All of these "u" names relate to the fact that the variable is unsigned,
which is a convention that the Linux kernel doesn't follow.  If you are
going to fix up the variable names, you may as well do it completely, ie
remove this problem as well.

julia


  reply	other threads:[~2020-03-26  7:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26  1:28 [Outreachy][PATCH] staging: vt6655: Replace camel case variable names Briana Oursler
2020-03-26  7:17 ` Julia Lawall [this message]
2020-03-26 19:46   ` [PATCH v2] " Briana Oursler
2020-03-26 20:14     ` Briana Oursler
2020-03-26 20:53   ` [PATCH v3] " Briana Oursler
2020-03-27  9:04     ` Greg KH
2020-03-28  4:38       ` [patch v4] " Briana Oursler
2020-03-30  7:04         ` [Outreachy kernel] " Stefano Brivio

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.21.2003260814590.3019@hadrien \
    --to=julia.lawall@inria.fr \
    --cc=briana.oursler@gmail.com \
    --cc=forest@alittletooquiet.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=outreachy-kernel@googlegroups.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.