public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Pavan Bobba <opensource206@gmail.com>
Cc: Julia Lawall <julia.lawall@inria.fr>,
	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: Mon, 14 Aug 2023 17:20:40 +0200	[thread overview]
Message-ID: <2023081442-cartridge-thaw-1656@gregkh> (raw)
In-Reply-To: <ZNolyVLwygowAzE2@ubuntu.myguest.virtualbox.org>

On Mon, Aug 14, 2023 at 06:32:01PM +0530, Pavan Bobba wrote:
> On Sat, Aug 12, 2023 at 08:41:51PM +0200, Julia Lawall wrote:
> > 
> > 
> > On Sat, 12 Aug 2023, Pavan Bobba wrote:
> > 
> > > On Fri, Aug 11, 2023 at 11:27:10PM +0200, Greg KH wrote:
> > > > On Wed, Aug 09, 2023 at 06:17:22PM +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. array name renamed from byVT3253B0_RFMD to by_vt3253b0_rfmd
> > > > >            2. typo in the subject line "small case" corrected with the
> > > > >               proper word "snake case"
> > > > >
> > > > > Signed-off-by: Pavan Bobba <opensource206@gmail.com>
> > > > > ---
> > > > >  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..cc8793256661 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 by_vt3253b0_rfmd[CB_VT3253B0_INIT_FOR_RFMD][2] = {
> > > >
> > > > Again, the "by" needs to just be dropped.
> > > >
> > > > thanks,
> > > >
> > > > greg k-h
> > >
> > > hi greg...did'nt get your comment. can you please provide more elaborate
> > > info?
> > 
> > Drop the letter "by_" at the beginning of the function name.  It is there
> > ot indicate the type, which isn't done in the kernel.
> > 
> > julia
> 
> this is'nt a function name but an array name. is in't it fine?
> 

Not at all.  The issue is the name, why are you just adding a "_" here?
What does "by" mean?  (hint, this is a rhetorical question, I know, I
need you to figure it out so you know how to properly rename the
variable here...)

thanks,

greg k-h

  reply	other threads:[~2023-08-14 15:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-09 12:47 [PATCH v2] staging: vt6655: replace camel case by snake case Pavan Bobba
2023-08-11 21:27 ` Greg KH
2023-08-12 18:29   ` Pavan Bobba
2023-08-12 18:41     ` Julia Lawall
2023-08-14 13:02       ` Pavan Bobba
2023-08-14 15:20         ` Greg KH [this message]
2023-08-17 12:08           ` Pavan Bobba
  -- 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-05  8:59 Pavan Bobba
2023-08-05 16:30 ` Dan Carpenter
2023-08-09 12:20 ` Greg KH
2023-08-02 13:26 [PATCH] staging: vt6655: replace camel case by small case Pavan Bobba
2023-08-02 13:33 ` Dan Carpenter
2023-08-04 11:53   ` [PATCH v2] staging: vt6655: replace camel case by snake case Pavan Bobba
2023-08-04 12:01     ` Dan Carpenter
2023-08-04 13:22     ` 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=2023081442-cartridge-thaw-1656@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=forest@alittletooquiet.net \
    --cc=julia.lawall@inria.fr \
    --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