All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes.sorensen@gmail.com>
To: Melike Yurtoglu <aysemelikeyurtoglu@gmail.com>,
	 outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH 1/4] Staging: lustre: lnet: klnds: socklnd: Deleted space prohibited between function name and open parenthesis
Date: Fri, 20 Feb 2015 12:02:10 -0500	[thread overview]
Message-ID: <54E76892.207@gmail.com> (raw)
In-Reply-To: <1424446070-14232-1-git-send-email-aysemelikeyurtoglu@gmail.com>

On 02/20/15 10:27, Melike Yurtoglu wrote:
> WARNING: space prohibited between function name and open parenthesis '('
> checkpatch.pl warning in socklnd.c
> 
> Signed-off-by: Melike Yurtoglu <aysemelikeyurtoglu@gmail.com>
> ---
>  .../staging/lustre/lnet/klnds/socklnd/socklnd.c    | 448 ++++++++++-----------
>  1 file changed, 224 insertions(+), 224 deletions(-)

When posting multi patch series, you need to use a cover letter to
describe the reason for the patch set. Argument '--cover-letter' for
'git format-patch'

In addition, please try to write a human patch description for each
commit rather than just paste in the automated checkpatch output.
Something like:

"Remove unnecessary space between function name and opening parenthesis.
That was found by running checkpatch.

Cheers,
Jes


> diff --git a/drivers/staging/lustre/lnet/klnds/socklnd/socklnd.c b/drivers/staging/lustre/lnet/klnds/socklnd/socklnd.c
> index 5956dba..aac3a7d 100644
> --- a/drivers/staging/lustre/lnet/klnds/socklnd/socklnd.c
> +++ b/drivers/staging/lustre/lnet/klnds/socklnd/socklnd.c
> @@ -65,15 +65,15 @@ ksocknal_ip2iface(lnet_ni_t *ni, __u32 ip)
>  }
>  
>  static ksock_route_t *
> -ksocknal_create_route (__u32 ipaddr, int port)
> +ksocknal_create_route(__u32 ipaddr, int port)
>  {
>  	ksock_route_t *route;
>  
> -	LIBCFS_ALLOC (route, sizeof (*route));
> +	LIBCFS_ALLOC(route, sizeof(*route));
>  	if (route == NULL)
>  		return NULL;
>  
> -	atomic_set (&route->ksnr_refcount, 1);
> +	atomic_set(&route->ksnr_refcount, 1);
>  	route->ksnr_peer = NULL;
>  	route->ksnr_retry_interval = 0;	 /* OK to connect at any time */
>  	route->ksnr_ipaddr = ipaddr;
> @@ -89,43 +89,43 @@ ksocknal_create_route (__u32 ipaddr, int port)
>  }



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

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20 15:27 [PATCH 1/4] Staging: lustre: lnet: klnds: socklnd: Deleted space prohibited between function name and open parenthesis Melike Yurtoglu
2015-02-20 15:27 ` [PATCH 2/4] Staging: lustre: lnet: klnds: socklnd: removed suspect code indent for conditional statements Melike Yurtoglu
2015-02-20 15:27 ` [PATCH 3/4] Staging: lustre: lnet: klnds: socklnd: Remove return in void function Melike Yurtoglu
2015-02-20 15:27 ` [PATCH 4/4] Staging: lustre: lnet: klnds: socklnd: Add blank line after declarations Melike Yurtoglu
2015-02-20 17:22   ` [Outreachy kernel] " Julia Lawall
2015-02-20 17:02 ` Jes Sorensen [this message]
2015-02-20 17:25   ` [Outreachy kernel] [PATCH 1/4] Staging: lustre: lnet: klnds: socklnd: Deleted space prohibited between function name and open parenthesis Ayşe Melike Yurtoğlu
2015-02-20 17:28     ` Jes Sorensen
2015-02-26 18:16 ` 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=54E76892.207@gmail.com \
    --to=jes.sorensen@gmail.com \
    --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.