diff options
| author | Heinrich Schuchardt <[email protected]> | 2021-09-20 14:15:03 +0200 |
|---|---|---|
| committer | Ramon Fried <[email protected]> | 2021-09-28 18:50:55 +0300 |
| commit | 001615386aff815a8721f8acffefbc82e9dfd149 (patch) | |
| tree | 188f602e52b0160ab0431d0dab844e4d66d9ed10 | |
| parent | 785b857d99b3cd89576c280cfa3a8349c2fb7f4c (diff) | |
fs: avoid superfluous messages
Output like the following is quite irritating:
=> bootefi hello
Scanning disk mmc2.blk...
No valid Btrfs found
Bad magic number for SquashFS image.
** Unrecognized filesystem type **
Scanning disk mmc1.blk...
No valid Btrfs found
Bad magic number for SquashFS image.
** Unrecognized filesystem type **
Scanning disk mmc0.blk...
No valid Btrfs found
Bad magic number for SquashFS image.
** Unrecognized filesystem type **
Albeit a whole disk may be formatted with a filesystem in most cases
a partition table is used and the whole disk (partition number 0) doesn't
contain a filesytem. Some partitions may only contain a blob. Not seeing a
filesytem on the whole disk or on any partition is only worth a debug
message.
Signed-off-by: Heinrich Schuchardt <[email protected]>
Reviewed-by: Simon Glass <[email protected]>
| -rw-r--r-- | fs/fs.c | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -37,7 +37,7 @@ static int fs_type = FS_TYPE_ANY; static inline int fs_probe_unsupported(struct blk_desc *fs_dev_desc, struct disk_partition *fs_partition) { - log_err("** Unrecognized filesystem type **\n"); + log_debug("Unrecognized filesystem type\n"); return -1; } |
