From: Kevin Mulvey <kevin@kevinmulvey.net>
To: Chris Mason <clm@fb.com>, Josef Bacik <jbacik@fb.com>,
David Sterba <dsterba@suse.cz>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Kevin Mulvey <kmulvey@linux.com>
Subject: [PATCH] fix spacing in btrfs/inode.c
Date: Wed, 11 Feb 2015 21:17:22 -0500 [thread overview]
Message-ID: <1423707442-9485-1-git-send-email-kmulvey@linux.com> (raw)
This is a patch to inode.c that fixes some spacing errors found by checkpatch.pl
Signed-off-by: Kevin Mulvey <kmulvey@linux.com>
---
fs/btrfs/inode.c | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
index 8bf326a..6516839 100644
--- a/fs/btrfs/inode.c
+++ b/fs/btrfs/inode.c
@@ -4545,7 +4545,7 @@ int btrfs_cont_expand(struct inode *inode, loff_t oldsize, loff_t size)
break;
}
last_byte = min(extent_map_end(em), block_end);
- last_byte = ALIGN(last_byte , root->sectorsize);
+ last_byte = ALIGN(last_byte, root->sectorsize);
if (!test_bit(EXTENT_FLAG_PREALLOC, &em->flags)) {
struct extent_map *hole_em;
hole_size = last_byte - cur_offset;
@@ -8829,9 +8829,9 @@ static int btrfs_rename(struct inode *old_dir, struct dentry *old_dentry,
*/
trans = btrfs_start_transaction(root, 11);
if (IS_ERR(trans)) {
- ret = PTR_ERR(trans);
- goto out_notrans;
- }
+ ret = PTR_ERR(trans);
+ goto out_notrans;
+ }
if (dest != root)
btrfs_record_root_in_trans(trans, dest);
@@ -9324,7 +9324,7 @@ static int __btrfs_prealloc_file_range(struct inode *inode, int mode,
break;
}
btrfs_drop_extent_cache(inode, cur_offset,
- cur_offset + ins.offset -1, 0);
+ cur_offset + ins.offset - 1, 0);
em = alloc_extent_map();
if (!em) {
--
2.1.0
next reply other threads:[~2015-02-12 2:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 2:17 Kevin Mulvey [this message]
2015-02-12 9:43 ` [PATCH] fix spacing in btrfs/inode.c David Sterba
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=1423707442-9485-1-git-send-email-kmulvey@linux.com \
--to=kevin@kevinmulvey.net \
--cc=clm@fb.com \
--cc=dsterba@suse.cz \
--cc=jbacik@fb.com \
--cc=kmulvey@linux.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 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.