All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: outreachy-kernel@googlegroups.com, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [Outreachy kernel] [PATCH] staging: rtl8723bs: Remove camelcase in several files
Date: Thu, 08 Apr 2021 10:52:09 +0200	[thread overview]
Message-ID: <2284292.R3b5UFg5HO@localhost.localdomain> (raw)
In-Reply-To: <YG7AkJjSThRbb/f5@kroah.com>

On Thursday, April 8, 2021 10:36:32 AM CEST Greg KH wrote:
> On Thu, Apr 08, 2021 at 10:07:14AM +0200, Fabio M. De Francesco wrote:
> > Remove camelcase in a symbol that is used by several files.
> 
> What symbol?
> 

I'm not sure I understand what you are asking. You mean
that I have to specify the name of the variable that I changed?
Or you mean that I shouldn't use the term "symbol" but write
"variable", "function", "macro", and so on?

>
> > --- a/drivers/staging/rtl8723bs/include/rtw_pwrctrl.h
> > +++ b/drivers/staging/rtl8723bs/include/rtw_pwrctrl.h
> > @@ -203,7 +203,7 @@ struct pwrctrl_priv {
> >  	u8 LpsIdleCount;
> >  	u8 power_mgnt;
> >  	u8 org_power_mgnt;
> > -	u8 bFwCurrentInPSMode;
> > +	u8 b_fw_current_in_ps_mode;
> 
> The "b" here means "byte" so you can drop the "b_" as that means
> nothing, we do not use this type of notation in the kernel as the
> compiler can check it for us.
>

OK, I didn't know what the 'b' meant in this context. I'll drop it.

Thanks,

Fabio
 
> thanks,
> 
> greg k-h
> 





  reply	other threads:[~2021-04-08  8:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-08  8:07 [Outreachy kernel] [PATCH] staging: rtl8723bs: Remove camelcase in several files Fabio M. De Francesco
2021-04-08  8:36 ` Greg KH
2021-04-08  8:52   ` Fabio M. De Francesco [this message]
2021-04-08  8:54     ` Julia Lawall
2021-04-08  9:10       ` Fabio M. De Francesco
2021-04-08  8:53 ` Julia Lawall
2021-04-08  9:23   ` Fabio M. De Francesco

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=2284292.R3b5UFg5HO@localhost.localdomain \
    --to=fmdefrancesco@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --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.