mkfs_vfat: use bb_error_msg for logging, not bb_info_msg
authorDenys Vlasenko <vda.linux@googlemail.com>
Wed, 30 Mar 2016 14:23:10 +0000 (16:23 +0200)
committerDenys Vlasenko <vda.linux@googlemail.com>
Wed, 30 Mar 2016 14:23:10 +0000 (16:23 +0200)
This affects only a commented-out code section which searches for bad blocks

Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
util-linux/mkfs_vfat.c

index 7d81ed06d8326940cdd2d2da519a04ecad215909..d53c751eba3041913b65653d58b83a60b92ed17b 100644 (file)
@@ -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