All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Vatika Harlalka <vatikaharlalka@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH v2] Staging: fbtft: Remove unnecessary parenthesis and split lines to increase readability
Date: Mon, 16 Mar 2015 16:26:07 +0100	[thread overview]
Message-ID: <20150316152607.GC22971@kroah.com> (raw)
In-Reply-To: <20150315115705.GA28579@akanksha>

On Sun, Mar 15, 2015 at 05:27:05PM +0530, Vatika Harlalka wrote:
> Remove unnecessary parenthesis in condition statement and
> split lines to increase readability.
> 
> Signed-off-by: Vatika Harlalka <vatikaharlalka@gmail.com>
> ---
>  Changes in v2: Changed subject line to make it more
> 		descriptive.
>  drivers/staging/fbtft/fb_ra8875.c | 16 ++++++++++------
>  1 file changed, 10 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/staging/fbtft/fb_ra8875.c b/drivers/staging/fbtft/fb_ra8875.c
> index e21af6c..bc8ca1e 100644
> --- a/drivers/staging/fbtft/fb_ra8875.c
> +++ b/drivers/staging/fbtft/fb_ra8875.c
> @@ -72,12 +72,13 @@ static int init_display(struct fbtft_par *par)
>  
>  	fbtft_par_dbg(DEBUG_INIT_DISPLAY, par,
>  		"%s()\n", __func__);
> -	fbtft_par_dbg(DEBUG_INIT_DISPLAY, par,
> -		"display size %dx%d\n", par->info->var.xres, par->info->var.yres);
> +	fbtft_par_dbg(DEBUG_INIT_DISPLAY, par, "display size %dx%d\n",
> +			par->info->var.xres, par->info->var.yres);
>  
>  	par->fbtftops.reset(par);
>  
> -	if ((par->info->var.xres == 320) && (par->info->var.yres == 240)) {
> +	if (par->info->var.xres == 320 &&
> +		par->info->var.yres == 240) {

While yes, these () are not needed, it's good to keep them there, just
to be "obvious" as to what is going on.  So they are fine to leave
alone.

thanks,

greg k-h


      reply	other threads:[~2015-03-16 15:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-15 11:57 [PATCH v2] Staging: fbtft: Remove unnecessary parenthesis and split lines to increase readability Vatika Harlalka
2015-03-16 15:26 ` Greg KH [this message]

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=20150316152607.GC22971@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=vatikaharlalka@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.