diff options
author | Heinrich Schuchardt <heinrich.schuchardt@canonical.com> | 2021-09-20 14:15:03 +0200 |
---|---|---|
committer | Tom Rini <trini@konsulko.com> | 2021-09-24 12:09:46 -0400 |
commit | 3bd0e2caa974aa300aadad171abe741d6edbc3b3 (patch) | |
tree | 188f602e52b0160ab0431d0dab844e4d66d9ed10 /fs | |
parent | 9aab28b6f2c223912cc195833d1877ef70bfb5ba (diff) | |
download | u-boot-3bd0e2caa974aa300aadad171abe741d6edbc3b3.tar.gz u-boot-3bd0e2caa974aa300aadad171abe741d6edbc3b3.tar.bz2 u-boot-3bd0e2caa974aa300aadad171abe741d6edbc3b3.zip |
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 <heinrich.schuchardt@canonical.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'fs')
-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; } |