diff options
| author | David Sterba <dsterba@suse.cz> | 2014-05-15 16:48:20 +0200 |
|---|---|---|
| committer | Chris Mason <clm@fb.com> | 2014-06-09 17:20:53 -0700 |
| commit | 351fd3532159441e810d458a5b681090ff8449fd (patch) | |
| tree | 7c087b510bff35cfd9c9b8d21d6a2a56f3a68f32 /fs/btrfs/ordered-data.c | |
| parent | 7d78874273463a784759916fc3e0b4e2eb141c70 (diff) | |
| download | linux-351fd3532159441e810d458a5b681090ff8449fd.tar.bz2 | |
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/ordered-data.c')
| -rw-r--r-- | fs/btrfs/ordered-data.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/btrfs/ordered-data.c b/fs/btrfs/ordered-data.c index a94b05f72869..e12441c7cf1d 100644 --- a/fs/btrfs/ordered-data.c +++ b/fs/btrfs/ordered-data.c @@ -67,7 +67,7 @@ static void ordered_data_tree_panic(struct inode *inode, int errno, { struct btrfs_fs_info *fs_info = btrfs_sb(inode->i_sb); btrfs_panic(fs_info, errno, "Inconsistency in ordered tree at offset " - "%llu\n", offset); + "%llu", offset); } /* |