linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Tabrez khan <khan.tabrez21@gmail.com>
Cc: mchehab@kernel.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH] staging:bcm2048 : Add parentheses around  variable x
Date: Fri, 3 Feb 2017 13:12:54 +0300	[thread overview]
Message-ID: <20170203101254.GA4419@mwanda> (raw)
In-Reply-To: <1480758266-6160-1-git-send-email-khan.tabrez21@gmail.com>

On Sat, Dec 03, 2016 at 03:14:26PM +0530, Tabrez khan wrote:
> Add parentheses around variable x for the readability purpose.
> 

It's not really about readability...

regards,
dan carpenter

  parent reply	other threads:[~2017-02-03 10:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-03  9:44 [PATCH] staging:bcm2048 : Add parentheses around variable x Tabrez khan
2017-02-03  9:55 ` Mauro Carvalho Chehab
2017-02-03 10:12 ` Dan Carpenter [this message]
2017-02-15 17:26   ` Tabrez Khan

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=20170203101254.GA4419@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=khan.tabrez21@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).