From: "KaiLong Wang" <wangkailong@jari.cn>
To: mark@fasheh.com, jlbec@evilplan.org
Cc: ocfs2-devel@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH] ocfs2: Clean up errors in dlmunlock.c
Date: Fri, 13 Oct 2023 15:45:46 +0800 (GMT+08:00) [thread overview]
Message-ID: <f2d4ee9.96a.18b27ffa1db.Coremail.wangkailong@jari.cn> (raw)
Fix the following errors reported by checkpatch:
ERROR: spaces required around that '<' (ctx:VxV)
ERROR: spaces required around that '=' (ctx:VxV)
ERROR: space required before that '&' (ctx:OxV)
ERROR: spaces required around that '==' (ctx:VxV)
ERROR: spaces required around that ':' (ctx:VxE)
Signed-off-by: KaiLong Wang <wangkailong@jari.cn>
---
fs/ocfs2/dlm/dlmunlock.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/fs/ocfs2/dlm/dlmunlock.c b/fs/ocfs2/dlm/dlmunlock.c
index 7318e4794ef9..ac9b29b2a11f 100644
--- a/fs/ocfs2/dlm/dlmunlock.c
+++ b/fs/ocfs2/dlm/dlmunlock.c
@@ -184,8 +184,8 @@ static enum dlm_status dlmunlock_common(struct dlm_ctxt *dlm,
mlog(0, "%s:%.*s: clearing actions, %s\n",
dlm->name, res->lockname.len,
res->lockname.name,
- status==DLM_RECOVERING?"recovering":
- (status==DLM_MIGRATING?"migrating":
+ status == DLM_RECOVERING ? "recovering" :
+ (status == DLM_MIGRATING ? "migrating" :
(status == DLM_FORWARD ? "forward" :
"nolockmanager")));
actions = 0;
@@ -436,7 +436,7 @@ int dlm_unlock_lock_handler(struct o2net_msg *msg, u32 len, void *data,
goto not_found;
}
- queue=&res->granted;
+ queue = &res->granted;
spin_lock(&res->spinlock);
if (res->state & DLM_LOCK_RES_RECOVERING) {
spin_unlock(&res->spinlock);
@@ -459,7 +459,7 @@ int dlm_unlock_lock_handler(struct o2net_msg *msg, u32 len, void *data,
goto leave;
}
- for (i=0; i<3; i++) {
+ for (i = 0; i < 3; i++) {
list_for_each_entry(iter, queue, list) {
if (iter->ml.cookie == unlock->cookie &&
iter->ml.node == unlock->node_idx) {
--
2.17.1
reply other threads:[~2023-10-13 7:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=f2d4ee9.96a.18b27ffa1db.Coremail.wangkailong@jari.cn \
--to=wangkailong@jari.cn \
--cc=jlbec@evilplan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
/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®