From: Dan Carpenter <dan.carpenter@oracle.com>
To: Kent Overstreet <kent.overstreet@gmail.com>
Cc: Neil Brown <neilb@suse.com>,
linux-bcache@vger.kernel.org, linux-raid@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: [patch -next] bcache: cleanup indenting in bch_btree_insert_check_key()
Date: Tue, 5 Jan 2016 12:55:14 +0300 [thread overview]
Message-ID: <20160105095514.GD23619@mwanda> (raw)
This was causing a static checker complaint because the indenting wasn't
consistent. Also it used spaces instead of tabs.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
diff --git a/drivers/md/bcache/btree.c b/drivers/md/bcache/btree.c
index 22b9e34..d493913 100644
--- a/drivers/md/bcache/btree.c
+++ b/drivers/md/bcache/btree.c
@@ -2163,8 +2163,8 @@ int bch_btree_insert_check_key(struct btree *b, struct btree_op *op,
rw_lock(true, b, b->level);
if (b->key.ptr[0] != btree_ptr ||
- b->seq != seq + 1) {
- op->lock = b->level;
+ b->seq != seq + 1) {
+ op->lock = b->level;
goto out;
}
}
reply other threads:[~2016-01-05 9:55 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=20160105095514.GD23619@mwanda \
--to=dan.carpenter@oracle.com \
--cc=kent.overstreet@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.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).