All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Payal Kshirsagar <payal.s.kshirsagar.98@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [PATCH 2/3] [Outreachy kernel] staging: sm750fb: avoid camelcase structure fields
Date: Thu, 21 Mar 2019 20:05:47 +0100	[thread overview]
Message-ID: <20190321190547.GA23519@kroah.com> (raw)
In-Reply-To: <1553166709-12186-1-git-send-email-payal.s.kshirsagar.98@gmail.com>

On Thu, Mar 21, 2019 at 04:41:49PM +0530, Payal Kshirsagar wrote:
> Eliminate camelcase structure fields to fix the style issue – ‘avoid
> camelcase’.
> 
> Signed-off-by: Payal Kshirsagar <payal.s.kshirsagar.98@gmail.com>
> ---
>  drivers/staging/sm750fb/ddk750_mode.c | 52 +++++++++++++++++------------------
>  1 file changed, 26 insertions(+), 26 deletions(-)
> 
> diff --git a/drivers/staging/sm750fb/ddk750_mode.c b/drivers/staging/sm750fb/ddk750_mode.c
> index 5e35fec..b55cd96 100644
> --- a/drivers/staging/sm750fb/ddk750_mode.c
> +++ b/drivers/staging/sm750fb/ddk750_mode.c
> @@ -13,13 +13,13 @@
>   * HW only supports 7 predefined pixel clocks, and clock select is
>   * in bit 29:27 of Display Control register.
>   */
> -static unsigned long display_control_adjust_SM750LE(struct mode_parameter *pModeParam,
> +static unsigned long display_control_adjust_SM750LE(struct mode_parameter *p_mode_param,

Why did you put "p_" as the prefix here?

The original code is trying to use the horrible Hungarian Notation way
of naming variables (and doing a bad job of it), which is not needed in
the kernel at all.  No need to keep following that, this should just be
"mode_param", right?  We "know" it is a pointer by virtue that the
compiler will tell us if we get it wrong.

thanks,

greg k-h


  reply	other threads:[~2019-03-21 19:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-21 11:11 [PATCH 2/3] [Outreachy kernel] staging: sm750fb: avoid camelcase structure fields Payal Kshirsagar
2019-03-21 19:05 ` Greg KH [this message]
2019-03-22  2:54   ` Payal Kshirsagar

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=20190321190547.GA23519@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=payal.s.kshirsagar.98@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 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.