From: Tabrez khan <khan.tabrez21@gmail.com>
To: andreas.dilger@intel.com, jsimmons@infradead.org
Cc: gregkh@linuxfoundation.org, lustre-devel@lists.lustre.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH] staging : lustre : Remove braces from single-line body.
Date: Fri, 16 Dec 2016 19:59:31 +0530 [thread overview]
Message-ID: <1481898571-16842-1-git-send-email-khan.tabrez21@gmail.com> (raw)
Remove unnecessary braces {} for single while statement.
This warning is found using checkpatch.pl.
Signed-off-by: Tabrez khan <khan.tabrez21@gmail.com>
---
drivers/staging/lustre/lustre/obdclass/cl_io.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/lustre/lustre/obdclass/cl_io.c b/drivers/staging/lustre/lustre/obdclass/cl_io.c
index bc4b7b6..2daede8 100644
--- a/drivers/staging/lustre/lustre/obdclass/cl_io.c
+++ b/drivers/staging/lustre/lustre/obdclass/cl_io.c
@@ -1371,9 +1371,9 @@ int cl_sync_io_wait(const struct lu_env *env, struct cl_sync_io *anchor,
LASSERT(atomic_read(&anchor->csi_sync_nr) == 0);
/* wait until cl_sync_io_note() has done wakeup */
- while (unlikely(atomic_read(&anchor->csi_barrier) != 0)) {
+ while (unlikely(atomic_read(&anchor->csi_barrier) != 0))
cpu_relax();
- }
+
return rc;
}
--
2.7.4
next reply other threads:[~2016-12-16 14:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 14:29 Tabrez khan [this message]
2016-12-16 16:05 ` [PATCH] staging : lustre : Remove braces from single-line body Joe Perches
2016-12-16 17:23 ` [lustre-devel] " Xiong, Jinshan
-- strict thread matches above, loose matches on Subject: below --
2016-12-16 17:59 Tabrez khan
2016-12-16 18:43 ` Joe Perches
2016-12-16 18:53 ` Dan Carpenter
2016-12-16 19:19 ` Joe Perches
2016-12-28 14:10 Tabrez khan
2017-01-03 14:15 ` Greg KH
2016-12-29 20:02 [PATCH] staging:lustre:remove " Tabrez khan
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=1481898571-16842-1-git-send-email-khan.tabrez21@gmail.com \
--to=khan.tabrez21@gmail.com \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
/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;
as well as URLs for NNTP newsgroup(s).