From: Greg KH <gregkh@linuxfoundation.org>
To: Payal Kshirsagar <payal.s.kshirsagar.98@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [PATCH] [Outreachy kernel] staging: sm750fb: avoid camelcase
Date: Thu, 21 Mar 2019 08:18:31 +0100 [thread overview]
Message-ID: <20190321071831.GC28171@kroah.com> (raw)
In-Reply-To: <1553147475-6907-1-git-send-email-payal.s.kshirsagar.98@gmail.com>
On Thu, Mar 21, 2019 at 11:21:15AM +0530, Payal Kshirsagar wrote:
> Eliminate camelcase to meet the style.
Meet what style?
>
> Signed-off-by: Payal Kshirsagar <payal.s.kshirsagar.98@gmail.com>
> ---
> drivers/staging/sm750fb/ddk750_mode.c | 94 +++++++++++++++++------------------
> 1 file changed, 47 insertions(+), 47 deletions(-)
>
> diff --git a/drivers/staging/sm750fb/ddk750_mode.c b/drivers/staging/sm750fb/ddk750_mode.c
> index 4dac691..5dfa87d 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 displayControlAdjust_SM750LE(struct mode_parameter *pModeParam,
> - unsigned long dispControl)
> +static unsigned long display_control_adjust_SM750LE(struct mode_parameter *p_mode_param,
> + unsigned long disp_control)
Try doing only one type of fix per patch.
One to fix up structure fields, and then another one for function names.
Putting them all together makes it very hard to review. This should be
a patch series for this type of fix.
thanks,
greg k-h
next prev parent reply other threads:[~2019-03-21 7:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 5:51 [PATCH] [Outreachy kernel] staging: sm750fb: avoid camelcase Payal Kshirsagar
2019-03-21 7:18 ` Greg KH [this message]
2019-03-21 7:28 ` 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=20190321071831.GC28171@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.