summaryrefslogtreecommitdiffstats
path: root/fs/btrfs/extent-tree.c
diff options
context:
space:
mode:
authorDavid Sterba <dsterba@suse.cz>2014-05-15 16:48:20 +0200
committerChris Mason <clm@fb.com>2014-06-09 17:20:53 -0700
commit351fd3532159441e810d458a5b681090ff8449fd (patch)
tree7c087b510bff35cfd9c9b8d21d6a2a56f3a68f32 /fs/btrfs/extent-tree.c
parent7d78874273463a784759916fc3e0b4e2eb141c70 (diff)
downloadop-kernel-dev-351fd3532159441e810d458a5b681090ff8449fd.zip
op-kernel-dev-351fd3532159441e810d458a5b681090ff8449fd.tar.gz
btrfs: remove stale newlines from log messages
I've noticed an extra line after "use no compression", but search revealed much more in messages of more critical levels and rare errors. Signed-off-by: David Sterba <dsterba@suse.cz> Signed-off-by: Chris Mason <clm@fb.com>
Diffstat (limited to 'fs/btrfs/extent-tree.c')
-rw-r--r--fs/btrfs/extent-tree.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
index ddf16bf..bb5b306 100644
--- a/fs/btrfs/extent-tree.c
+++ b/fs/btrfs/extent-tree.c
@@ -5932,7 +5932,7 @@ static int __btrfs_free_extent(struct btrfs_trans_handle *trans,
refs = btrfs_extent_refs(leaf, ei);
if (refs < refs_to_drop) {
btrfs_err(info, "trying to drop %d refs but we only have %Lu "
- "for bytenr %Lu\n", refs_to_drop, refs, bytenr);
+ "for bytenr %Lu", refs_to_drop, refs, bytenr);
ret = -EINVAL;
btrfs_abort_transaction(trans, extent_root, ret);
goto out;
OpenPOWER on IntegriCloud