All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Melike Yurtoglu <aysemelikeyurtoglu@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH v2 1/4] Staging: lustre: Deleted space prohibited between function name and open parenthesis
Date: Thu, 26 Feb 2015 10:20:02 -0800	[thread overview]
Message-ID: <20150226182002.GA7025@kroah.com> (raw)
In-Reply-To: <1424462647-4861-1-git-send-email-aysemelikeyurtoglu@gmail.com>

On Fri, Feb 20, 2015 at 10:04:04PM +0200, Melike Yurtoglu wrote:
> WARNING: space prohibited between function name and open parenthesis '('
> Remove unnecessary space between function name and opening parenthesis.
> That was found by running checkpatch
> 
> Signed-off-by: Melike Yurtoglu <aysemelikeyurtoglu@gmail.com>
> ---
> 
> v2:changed the subject line and description
> 
>  .../staging/lustre/lnet/klnds/socklnd/socklnd.c    | 448 ++++++++++-----------
>  1 file changed, 224 insertions(+), 224 deletions(-)

Did you test this version?  I hesitate to even apply it considering I
don't think you did :)

Please fix up and resend.

thanks,

greg k-h


  parent reply	other threads:[~2015-02-26 18:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20 20:04 [PATCH v2 1/4] Staging: lustre: Deleted space prohibited between function name and open parenthesis Melike Yurtoglu
2015-02-20 20:04 ` [PATCH v2 2/4] Staging: lustre: removed suspect code indent for conditional statements Melike Yurtoglu
2015-02-20 20:04 ` [PATCH v2 3/4] Staging: lustre: Remove return in void function Melike Yurtoglu
2015-02-20 20:04 ` [PATCH v2 4/4] Staging: lustre: Add blank line after declarations Melike Yurtoglu
2015-02-26 18:20 ` Greg KH [this message]
2015-02-26 23:40   ` [Outreachy kernel] [PATCH v2 1/4] Staging: lustre: Deleted space prohibited between function name and open parenthesis Ayşe Melike Yurtoğlu
2015-02-26 23:58     ` Greg KH

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=20150226182002.GA7025@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=aysemelikeyurtoglu@gmail.com \
    --cc=outreachy-kernel@googlegroups.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.