From: Dorcas Litunya <anonolitunya@gmail.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: outreachy@lists.linux.dev,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Teddy Wang <teddy.wang@siliconmotion.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-fbdev@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [PATCH]Staging: sm750fb:Add snakecase naming style
Date: Fri, 13 Oct 2023 14:33:00 +0300 [thread overview]
Message-ID: <ZSkq7E+Tp1X/qiER@dorcaslitunya-virtual-machine> (raw)
In-Reply-To: <efcb4734-0349-493e-be93-b95381eb6c78@kadam.mountain>
On Fri, Oct 13, 2023 at 01:48:08PM +0300, Dan Carpenter wrote:
> On Fri, Oct 13, 2023 at 01:42:15PM +0300, Dorcas AnonoLitunya wrote:
> > From: Dorcas Anono Litunya <anonolitunya@gmail.com>
> >
> > Change camelCase variables in file to snake_case for consistent naming
> > practices. Issue found by checkpatch.
> >
> > Signed-off-by: Dorcas Anono Litunya <anonolitunya@gmail.com>
> > ---
> > drivers/staging/sm750fb/ddk750_mode.c | 86 +++++++++++++--------------
> > drivers/staging/sm750fb/ddk750_mode.h | 2 +-
> > drivers/staging/sm750fb/sm750_hw.c | 2 +-
> > 3 files changed, 45 insertions(+), 45 deletions(-)
> >
> > diff --git a/drivers/staging/sm750fb/ddk750_mode.c b/drivers/staging/sm750fb/ddk750_mode.c
> > index e00a6cb31947..f08dcab29172 100644
> > --- a/drivers/staging/sm750fb/ddk750_mode.c
> > +++ b/drivers/staging/sm750fb/ddk750_mode.c
> > @@ -14,13 +14,13 @@
> > * in bit 29:27 of Display Control register.
> > */
> > static unsigned long
> > -displayControlAdjust_SM750LE(struct mode_parameter *pModeParam,
> > - unsigned long dispControl)
> > +display_control_adjust_SM750LE(struct mode_parameter *p_mode_param,
>
> The p stands for pointer. We don't like that naming style. Just call
> it mode_param.
>
> Thes are the renamed things.
>
> displayControlAdjust_SM750LE => display_control_adjust_SM750LE
> pModeParam => p_mode_param
> dispControl => disp_control
> programModeRegisters => program_mode_registers
> ddk750_setModeTiming => ddk750_set_mode_timing
>
> I feel like this would be better broken up probably into one variable
> per patch. It's jumping around between files. These variables are not
> closely related.
Thanks for the feedback Dan. I will revise to do one variable per patch.
However,I have an inquiry the main reason its jumping between files is because one of the
functions I am modifying(the ddk_set_mode_timing) is imported and used
in other files. In this case, should I do one patch per variable per
file?
Dorcas
>
> regards,
> dan carpenter
>
next prev parent reply other threads:[~2023-10-13 15:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 10:42 [PATCH] [PATCH]Staging: sm750fb:Add snakecase naming style Dorcas AnonoLitunya
2023-10-13 10:48 ` Dan Carpenter
2023-10-13 11:33 ` Dorcas Litunya [this message]
2023-10-13 15:56 ` Dan Carpenter
2023-10-13 11:46 ` Dorcas Litunya
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=ZSkq7E+Tp1X/qiER@dorcaslitunya-virtual-machine \
--to=anonolitunya@gmail.com \
--cc=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
--cc=sudipm.mukherjee@gmail.com \
--cc=teddy.wang@siliconmotion.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