From: Julian Geus <julian.geus@fau.de>
To: oleg.drokin@intel.com
Cc: andreas.dilger@intel.com, jsimmons@infradead.org,
gregkh@linuxfoundation.org, neilb@suse.com, koskisoft@gmail.com,
aastha.gupta4104@gmail.com, andriy.skulysh@seagate.com,
bcodding@redhat.com, lustre-devel@lists.lustre.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
linux-kernel@i4.cs.fau.de, Julian Geus <julian.geus@fau.de>,
Kilian Bender <kilian.bender.kernel@gmail.com>
Subject: [PATCH] Changed misspelled variable name
Date: Fri, 22 Dec 2017 12:11:24 +0100 [thread overview]
Message-ID: <1513941084-11828-1-git-send-email-julian.geus@fau.de> (raw)
The misspelled variable name 'splitted' was changed into 'split'.
Signed-off-by: Julian Geus <julian.geus@fau.de>
Signed-off-by: Kilian Bender <kilian.bender.kernel@gmail.com>
---
drivers/staging/lustre/lustre/ldlm/ldlm_flock.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/lustre/lustre/ldlm/ldlm_flock.c b/drivers/staging/lustre/lustre/ldlm/ldlm_flock.c
index 657ab95..782d8da 100644
--- a/drivers/staging/lustre/lustre/ldlm/ldlm_flock.c
+++ b/drivers/staging/lustre/lustre/ldlm/ldlm_flock.c
@@ -121,7 +121,7 @@ static int ldlm_process_flock_lock(struct ldlm_lock *req)
struct ldlm_lock *new2 = NULL;
enum ldlm_mode mode = req->l_req_mode;
int added = (mode == LCK_NL);
- int splitted = 0;
+ int split = 0;
const struct ldlm_callback_suite null_cbs = { };
CDEBUG(D_DLMTRACE,
@@ -249,7 +249,7 @@ static int ldlm_process_flock_lock(struct ldlm_lock *req)
goto reprocess;
}
- splitted = 1;
+ split = 1;
new2->l_granted_mode = lock->l_granted_mode;
new2->l_policy_data.l_flock.pid =
@@ -282,7 +282,7 @@ static int ldlm_process_flock_lock(struct ldlm_lock *req)
}
/* if new2 is created but never used, destroy it*/
- if (splitted == 0 && new2)
+ if (split == 0 && new2)
ldlm_lock_destroy_nolock(new2);
/* At this point we're granting the lock request. */
--
2.7.4
reply other threads:[~2017-12-22 11:17 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=1513941084-11828-1-git-send-email-julian.geus@fau.de \
--to=julian.geus@fau.de \
--cc=aastha.gupta4104@gmail.com \
--cc=andreas.dilger@intel.com \
--cc=andriy.skulysh@seagate.com \
--cc=bcodding@redhat.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jsimmons@infradead.org \
--cc=kilian.bender.kernel@gmail.com \
--cc=koskisoft@gmail.com \
--cc=linux-kernel@i4.cs.fau.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=neilb@suse.com \
--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;
as well as URLs for NNTP newsgroup(s).