All of lore.kernel.org
 help / color / mirror / Atom feed
From: MonamAgarwal <monamagarwal123@gmail.com>
To: gregkh@linuxfoundation.org, rashika.kheria@gmail.com,
	peter.p.waskiewicz.jr@intel.com, monamagarwal123@gmail.com,
	andreas.dilger@intel.com, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] Staging: lustre: Fix return does not need parantheses
Date: Mon, 6 Jan 2014 01:48:07 +0530	[thread overview]
Message-ID: <52c9be03.c394420a.7a22.36eb@mx.google.com> (raw)

This patch fixes the following checkpatch.pl warning in
lustre/ldlm/interval_tree.c
ERROR: return is not a function, parentheses are not required

Signed-off-by: MonamAgarwal <monamagarwal123@gmail.com>
---
 drivers/staging/lustre/lustre/ldlm/interval_tree.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/staging/lustre/lustre/ldlm/interval_tree.c b/drivers/staging/lustre/lustre/ldlm/interval_tree.c
index f61bf19..9338203 100644
--- a/drivers/staging/lustre/lustre/ldlm/interval_tree.c
+++ b/drivers/staging/lustre/lustre/ldlm/interval_tree.c
@@ -578,8 +578,8 @@ EXPORT_SYMBOL(interval_erase);
 static inline int interval_may_overlap(struct interval_node *node,
 					  struct interval_node_extent *ext)
 {
-	return (ext->start <= node->in_max_high &&
-		ext->end >= interval_low(node));
+	return ext->start <= node->in_max_high &&
+		ext->end >= interval_low(node);
 }

 /*
--
1.7.9.5


             reply	other threads:[~2014-01-05 20:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-05 20:18 MonamAgarwal [this message]
2014-01-08 23:56 ` [PATCH 2/2] Staging: lustre: Fix return does not need parantheses 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=52c9be03.c394420a.7a22.36eb@mx.google.com \
    --to=monamagarwal123@gmail.com \
    --cc=andreas.dilger@intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.p.waskiewicz.jr@intel.com \
    --cc=rashika.kheria@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.