From: aybuke ozdemir <aybuke.147@gmail.com>
To: outreachy-kernel@googlegroups.com
Cc: aybuke ozdemir <aybuke.147@gmail.com>
Subject: [PATCH 3/5] Staging: lustre: Corrected code indentation
Date: Sat, 21 Feb 2015 13:44:33 +0200 [thread overview]
Message-ID: <1424519075-4378-3-git-send-email-aybuke.147@gmail.com> (raw)
In-Reply-To: <1424519075-4378-1-git-send-email-aybuke.147@gmail.com>
This patch fixes these warning messages found by checkpatch.pl:
WARNING: suspect code indent for conditional statements(8,15)
Signed-off-by: aybuke ozdemir <aybuke.147@gmail.com>
---
drivers/staging/lustre/lustre/llite/file.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/lustre/lustre/llite/file.c b/drivers/staging/lustre/lustre/llite/file.c
index 845589f..9a7ab65 100644
--- a/drivers/staging/lustre/lustre/llite/file.c
+++ b/drivers/staging/lustre/lustre/llite/file.c
@@ -2822,7 +2822,7 @@ int ll_have_md_lock(struct inode *inode, __u64 *bits, ldlm_mode_t l_req_mode)
int i;
if (!inode)
- return 0;
+ return 0;
fid = &ll_i2info(inode)->lli_fid;
CDEBUG(D_INFO, "trying to match res "DFID" mode %s\n", PFID(fid),
--
1.9.1
next prev parent reply other threads:[~2015-02-21 11:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-21 11:44 [PATCH 1/5] Staging: lustre: Move export_symbol below its function aybuke ozdemir
2015-02-21 11:44 ` [PATCH 2/5] Staging: lustre: Added blank line after declarations aybuke ozdemir
2015-02-21 11:44 ` aybuke ozdemir [this message]
2015-02-21 14:57 ` [Outreachy kernel] [PATCH 3/5] Staging: lustre: Corrected code indentation Julia Lawall
2015-02-21 11:44 ` [PATCH 4/5] Staging: lustre: Added spaces around '=' aybuke ozdemir
2015-02-21 14:57 ` [Outreachy kernel] " Julia Lawall
2015-02-21 11:44 ` [PATCH 5/5] Staging: lustre: Remove space after the name of that function aybuke ozdemir
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=1424519075-4378-3-git-send-email-aybuke.147@gmail.com \
--to=aybuke.147@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.