diff options
| author | David Sterba <dsterba@suse.cz> | 2014-05-15 18:48:20 +0400 |
|---|---|---|
| committer | Chris Mason <clm@fb.com> | 2014-06-10 04:20:53 +0400 |
| commit | 351fd3532159441e810d458a5b681090ff8449fd (patch) | |
| tree | 7c087b510bff35cfd9c9b8d21d6a2a56f3a68f32 /fs/btrfs/send.c | |
| parent | 7d78874273463a784759916fc3e0b4e2eb141c70 (diff) | |
| download | linux-351fd3532159441e810d458a5b681090ff8449fd.tar.xz | |
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/send.c')
| -rw-r--r-- | fs/btrfs/send.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/fs/btrfs/send.c b/fs/btrfs/send.c index 3f14b31c0c96..a86c049932f9 100644 --- a/fs/btrfs/send.c +++ b/fs/btrfs/send.c @@ -1349,7 +1349,7 @@ static int find_extent_clone(struct send_ctx *sctx, ret = -EIO; btrfs_err(sctx->send_root->fs_info, "did not find backref in " "send_root. inode=%llu, offset=%llu, " - "disk_byte=%llu found extent=%llu\n", + "disk_byte=%llu found extent=%llu", ino, data_offset, disk_byte, found_key.objectid); goto out; } @@ -5472,7 +5472,7 @@ static void btrfs_root_dec_send_in_progress(struct btrfs_root* root) */ if (root->send_in_progress < 0) btrfs_err(root->fs_info, - "send_in_progres unbalanced %d root %llu\n", + "send_in_progres unbalanced %d root %llu", root->send_in_progress, root->root_key.objectid); spin_unlock(&root->root_item_lock); } |