From: Philippe Loctaux <phil@philippeloctaux.com>
To: clm@fb.com
Cc: jbacik@fb.com, dsterba@suse.com, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org,
Philippe Loctaux <phil@philippeloctaux.com>
Subject: [PATCH 1/3] Btrfs: disk-io: fixed a brace coding style issue
Date: Mon, 22 Feb 2016 11:18:06 +0100 [thread overview]
Message-ID: <1456136288-4718-1-git-send-email-phil@philippeloctaux.com> (raw)
Fixed a coding style issue.
Signed-off-by: Philippe Loctaux <phil@philippeloctaux.com>
---
fs/btrfs/disk-io.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
index 4545e2e..84cbf16 100644
--- a/fs/btrfs/disk-io.c
+++ b/fs/btrfs/disk-io.c
@@ -1908,11 +1908,11 @@ static int transaction_kthread(void *arg)
cannot_commit = true;
goto sleep;
}
- if (transid == trans->transid) {
+ if (transid == trans->transid)
btrfs_commit_transaction(trans, root);
- } else {
+ else
btrfs_end_transaction(trans, root);
- }
+
sleep:
wake_up_process(root->fs_info->cleaner_kthread);
mutex_unlock(&root->fs_info->transaction_kthread_mutex);
@@ -1978,11 +1978,11 @@ static void find_oldest_super_backup(struct btrfs_fs_info *info,
newest_index = find_newest_super_backup(info, newest_gen);
/* if there was garbage in there, just move along */
- if (newest_index == -1) {
+ if (newest_index == -1)
info->backup_root_index = 0;
- } else {
+ else
info->backup_root_index = (newest_index + 1) % BTRFS_NUM_BACKUP_ROOTS;
- }
+
}
/*
--
2.7.1
next reply other threads:[~2016-02-22 10:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 10:18 Philippe Loctaux [this message]
2016-02-22 10:18 ` [PATCH 2/3] Btrfs: disk-io: fixed an assignment error Philippe Loctaux
2016-02-22 10:18 ` [PATCH 3/3] Btrfs: disk-io: fixed a comment block coding style issue Philippe Loctaux
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=1456136288-4718-1-git-send-email-phil@philippeloctaux.com \
--to=phil@philippeloctaux.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).