public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Pavan Bobba <opensource206@gmail.com>
Cc: Forest Bond <forest@alittletooquiet.net>,
	Michael Straube <straube.linux@gmail.com>,
	Philipp Hortmann <philipp.g.hortmann@gmail.com>,
	outreachy@lists.linux.dev, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: vt6655: replace camel case by snake case
Date: Wed, 9 Aug 2023 14:20:18 +0200	[thread overview]
Message-ID: <2023080918-opulently-eclipse-7555@gregkh> (raw)
In-Reply-To: <ZM4PWL55pMQiYIX6@ubuntu.myguest.virtualbox.org>

On Sat, Aug 05, 2023 at 02:29:04PM +0530, Pavan Bobba wrote:
> Replace array name of camel case by snake case. Issue found
> by checkpatch
> 
> Signed-off-by: Pavan Bobba <opensource206@gmail.com>
> ---
>  v1 -> v2: 1.character '_' added in the array name "byvt3253b0_rfmde"
>            2. typo in the subject line "small case" corrected with the
> 	      proper word "snake case"
> 
>  drivers/staging/vt6655/baseband.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/staging/vt6655/baseband.c b/drivers/staging/vt6655/baseband.c
> index 0e135af8316b..8b913c64845c 100644
> --- a/drivers/staging/vt6655/baseband.c
> +++ b/drivers/staging/vt6655/baseband.c
> @@ -499,7 +499,7 @@ static const unsigned char by_vt3253_init_tab_rfmd[CB_VT3253_INIT_FOR_RFMD][2] =
>  };
>  
>  #define CB_VT3253B0_INIT_FOR_RFMD 256
> -static const unsigned char byVT3253B0_RFMD[CB_VT3253B0_INIT_FOR_RFMD][2] = {
> +static const unsigned char byvt3253b0_rfmd[CB_VT3253B0_INIT_FOR_RFMD][2] = {

The "by" here means "byte", a horrible naming scheme that was popular in
the 1990's when C compilers would not check the types of variables.  No
need for that here, this should just be "vt3253b0_rfmd", right?

thanks,

greg k-h

  parent reply	other threads:[~2023-08-09 12:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-05  8:59 [PATCH v2] staging: vt6655: replace camel case by snake case Pavan Bobba
2023-08-05 16:30 ` Dan Carpenter
2023-08-09 12:20 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-23 12:53 Pavan Bobba
2023-08-23 12:58 ` Julia Lawall
2023-08-23 13:32   ` Pavan Bobba
2023-08-23 13:58 ` Greg KH
2023-08-09 12:47 Pavan Bobba
2023-08-11 21:27 ` Greg KH
     [not found]   ` <ZNfPiQAL3ixA7tjz@ubuntu.myguest.virtualbox.org>
     [not found]     ` <alpine.DEB.2.22.394.2308122041160.3315@hadrien>
2023-08-14 13:02       ` Pavan Bobba
2023-08-14 15:20         ` Greg KH
2023-08-17 12:08           ` Pavan Bobba
2023-08-03 15:27 Pavan Bobba
2023-08-03 15:34 ` Greg Kroah-Hartman
2023-08-04 13:23 ` Greg Kroah-Hartman

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=2023080918-opulently-eclipse-7555@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=forest@alittletooquiet.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=opensource206@gmail.com \
    --cc=outreachy@lists.linux.dev \
    --cc=philipp.g.hortmann@gmail.com \
    --cc=straube.linux@gmail.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