public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Junien Fridrick <linux.kernel@junien.fridrick.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Lai Siyao <lai.siyao@intel.com>,
	Oleg Drokin <oleg.drokin@intel.com>,
	"John L. Hammond" <john.hammond@intel.com>,
	Jinshan Xiong <jinshan.xiong@intel.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	Junien Fridrick <linux.kernel@junien.fridrick.net>
Subject: [PATCH v2] staging: lustre: fix coding style issue: missing space after 'if'
Date: Sun, 10 Aug 2014 23:05:38 +0000	[thread overview]
Message-ID: <1407711938-2046-1-git-send-email-linux.kernel@junien.fridrick.net> (raw)
In-Reply-To: <20140810122411.GF28863@kroah.com>

Coding style issue reported by checkpatch.pl

Signed-off-by: Junien Fridrick <linux.kernel@junien.fridrick.net>
---
This patch is part of task 10 of the eudyptula challenge
Applies to next-20140808

v2 : fixed patch short summary and description

 drivers/staging/lustre/lustre/llite/remote_perm.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/staging/lustre/lustre/llite/remote_perm.c b/drivers/staging/lustre/lustre/llite/remote_perm.c
index f61fefc..3a9c8e8 100644
--- a/drivers/staging/lustre/lustre/llite/remote_perm.c
+++ b/drivers/staging/lustre/lustre/llite/remote_perm.c
@@ -100,7 +100,7 @@ void free_rmtperm_hash(struct hlist_head *hash)
 	struct ll_remote_perm *lrp;
 	struct hlist_node *next;
 
-	if(!hash)
+	if (!hash)
 		return;
 
 	for (i = 0; i < REMOTE_PERM_HASHSIZE; i++)
-- 
2.0.1


      reply	other threads:[~2014-08-10 23:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-09 20:22 [PATCH] [next-20140808] [staging] [lustre] Fix coding style in llite/remote_perm.c Junien Fridrick
2014-08-09 22:50 ` Aaro Koskinen
2014-08-10 12:24 ` Greg Kroah-Hartman
2014-08-10 23:05   ` Junien Fridrick [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=1407711938-2046-1-git-send-email-linux.kernel@junien.fridrick.net \
    --to=linux.kernel@junien.fridrick.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jinshan.xiong@intel.com \
    --cc=john.hammond@intel.com \
    --cc=lai.siyao@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg.drokin@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox