All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis de Bethencourt <luisbg@osg.samsung.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] staging: i4l: icn: do not use return as a function
Date: Wed, 15 Jun 2016 21:29:38 +0100	[thread overview]
Message-ID: <5761BAB2.8000505@osg.samsung.com> (raw)
In-Reply-To: <1465679455-21152-1-git-send-email-sudipm.mukherjee@gmail.com>

On 11/06/16 22:10, Sudip Mukherjee wrote:
> return is not a function so no need to use the parenthesis.
> 
> Signed-off-by: Sudip Mukherjee <sudip.mukherjee@codethink.co.uk>
> ---
>  drivers/staging/i4l/icn/icn.c | 16 ++++++++--------
>  1 file changed, 8 insertions(+), 8 deletions(-)
> 

All the patches in this series look like good style fixes to me.

Thanks Sudip :)
Luis

  parent reply	other threads:[~2016-06-15 20:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-11 21:10 [PATCH 1/6] staging: i4l: icn: do not use return as a function Sudip Mukherjee
2016-06-11 21:10 ` [PATCH 2/6] staging: i4l: icn: donot assign in if statement Sudip Mukherjee
2016-06-11 21:10 ` [PATCH 3/6] staging: i4l: icn: space not needed after cast Sudip Mukherjee
2016-06-11 21:10 ` [PATCH 4/6] staging: i4l: icn: remove braces Sudip Mukherjee
2016-06-11 21:10 ` [PATCH 5/6] staging: i4l: icn: remove blank lines Sudip Mukherjee
2016-06-11 21:10 ` [PATCH 6/6] staging: i4l: icn: fix incorrect type of arguments Sudip Mukherjee
2016-06-11 21:14   ` [PATCH 6/6 v2] " Sudip Mukherjee
2016-06-15 20:29 ` Luis de Bethencourt [this message]
2016-08-21 15:22 ` [PATCH 1/6] staging: i4l: icn: do not use return as a function Greg Kroah-Hartman

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=5761BAB2.8000505@osg.samsung.com \
    --to=luisbg@osg.samsung.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sudipm.mukherjee@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.