From 3b757f07982b38b7a550c10ca37c9d173d450cac Mon Sep 17 00:00:00 2001 From: Denys Vlasenko Date: Wed, 30 Mar 2016 16:23:10 +0200 Subject: mkfs_vfat: use bb_error_msg for logging, not bb_info_msg This affects only a commented-out code section which searches for bad blocks Signed-off-by: Denys Vlasenko --- util-linux/mkfs_vfat.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'util-linux/mkfs_vfat.c') diff --git a/util-linux/mkfs_vfat.c b/util-linux/mkfs_vfat.c index 7d81ed06d..d53c751eb 100644 --- a/util-linux/mkfs_vfat.c +++ b/util-linux/mkfs_vfat.c @@ -578,7 +578,7 @@ int mkfs_vfat_main(int argc UNUSED_PARAM, char **argv) start_data_sector = (reserved_sect + NUM_FATS * sect_per_fat) * (bytes_per_sect / SECTOR_SIZE); start_data_block = (start_data_sector + SECTORS_PER_BLOCK - 1) / SECTORS_PER_BLOCK; - bb_info_msg("searching for bad blocks "); + bb_error_msg("searching for bad blocks"); currently_testing = 0; try = TEST_BUFFER_BLOCKS; while (currently_testing < volume_size_blocks) { @@ -616,7 +616,7 @@ int mkfs_vfat_main(int argc UNUSED_PARAM, char **argv) } free(blkbuf); if (badblocks) - bb_info_msg("%d bad block(s)", badblocks); + bb_error_msg("%d bad block(s)", badblocks); } #endif -- cgit v1.2.3