mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Anjali Menon <cse.anjalimenon@gmail.com>
To: gregkh@linuxfoundation.org
Cc: oleg.drokin@intel.com, andreas.dilger@intel.com,
	HPDD-discuss@lists.01.orgn, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org,
	Anjali Menon <cse.anjalimenon@gmail.com>
Subject: [PATCH] staging: lustre: lustre: libcfs: Removed a space
Date: Sun, 20 Sep 2015 22:59:16 +0530	[thread overview]
Message-ID: <1442770156-7580-1-git-send-email-cse.anjalimenon@gmail.com> (raw)

Removed space between function name and open paranthesis
detected by checkpatch.pl

112: WARNING: space prohibited between function name and open
parenthesis '('
152: WARNING: space prohibited between function name and open
parenthesis '('
164: WARNING: space prohibited between function name and open
parenthesis '('
165: WARNING: space prohibited between function name and open
parenthesis '('
345: WARNING: space prohibited between function name and open
parenthesis '('
447: WARNING: space prohibited between function name and open
parenthesis '('

Signed-off-by: Anjali Menon <cse.anjalimenon@gmail.com>
---
 drivers/staging/lustre/lustre/libcfs/module.c | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/drivers/staging/lustre/lustre/libcfs/module.c b/drivers/staging/lustre/lustre/libcfs/module.c
index 7d0427b..4216592 100644
--- a/drivers/staging/lustre/lustre/libcfs/module.c
+++ b/drivers/staging/lustre/lustre/libcfs/module.c
@@ -109,7 +109,7 @@ enum {
 	PSDEV_LNET_FAIL_VAL,      /* userdata for fail loc */
 };
 
-static void kportal_memhog_free (struct libcfs_device_userstate *ldu)
+static void kportal_memhog_free(struct libcfs_device_userstate *ldu)
 {
 	struct page **level0p = &ldu->ldu_memhog_root_page;
 	struct page **level1p;
@@ -149,7 +149,7 @@ static void kportal_memhog_free (struct libcfs_device_userstate *ldu)
 		*level0p = NULL;
 	}
 
-	LASSERT (ldu->ldu_memhog_pages == 0);
+	LASSERT(ldu->ldu_memhog_pages == 0);
 }
 
 static int kportal_memhog_alloc(struct libcfs_device_userstate *ldu, int npages,
@@ -161,8 +161,8 @@ static int kportal_memhog_alloc(struct libcfs_device_userstate *ldu, int npages,
 	int	   count1;
 	int	   count2;
 
-	LASSERT (ldu->ldu_memhog_pages == 0);
-	LASSERT (ldu->ldu_memhog_root_page == NULL);
+	LASSERT(ldu->ldu_memhog_pages == 0);
+	LASSERT(ldu->ldu_memhog_root_page == NULL);
 
 	if (npages < 0)
 		return -EINVAL;
@@ -342,7 +342,7 @@ static int libcfs_ioctl_int(struct cfs_psdev_file *pfile, unsigned long cmd,
 			if (err != -EINVAL) {
 				if (err == 0)
 					err = libcfs_ioctl_popdata(arg,
-							data, sizeof (*data));
+							data, sizeof(*data));
 				break;
 			}
 		}
@@ -444,7 +444,7 @@ static int init_libcfs_module(void)
 		goto cleanup_crypto;
 	}
 
-	CDEBUG (D_OTHER, "portals setup OK\n");
+	CDEBUG(D_OTHER, "portals setup OK\n");
 	return 0;
  cleanup_crypto:
 	cfs_crypto_unregister();
-- 
1.9.1


             reply	other threads:[~2015-09-20 17:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-20 17:29 Anjali Menon [this message]
2015-09-21  1:48 ` 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=1442770156-7580-1-git-send-email-cse.anjalimenon@gmail.com \
    --to=cse.anjalimenon@gmail.com \
    --cc=HPDD-discuss@lists.01.orgn \
    --cc=andreas.dilger@intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --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

all inboxes | Powered by JetHome®