[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <0EAA3AC5-9EB3-4547-AA50-0B601665B1C3@sun.com>
Date: Wed, 04 Nov 2009 21:50:57 -0700
From: Andreas Dilger <adilger@....com>
To: Alexey Fisher <bug-track@...her-privat.net>
Cc: Eric Sandeen <sandeen@...hat.com>, linux-ext4@...r.kernel.org
Subject: Re: [PATCH] make unified logs on ext2
On 2009-11-04, at 13:40, Alexey Fisher wrote:
> i trying to make messages produced by ext2 more unified. It should be
> easy to parse.
This patch follows the ext4_msg() changes in ext4, so at least it is
not inventing something different.
Reviewed-by: Andreas Dilger <adilger@....com>
Minor note:
> @@ -840,8 +858,9 @@ static int ext2_fill_super(struct super_block
> *sb, void *data, int silent)
> (EXT2_HAS_COMPAT_FEATURE(sb, ~0U) ||
> EXT2_HAS_RO_COMPAT_FEATURE(sb, ~0U) ||
> EXT2_HAS_INCOMPAT_FEATURE(sb, ~0U)))
> - printk("EXT2-fs warning: feature flags set on rev 0 fs, "
> - "running e2fsck is recommended\n");
> + ext2_msg(sb, KERN_WARNING,
> + "warning: feature flags set on rev 0 fs, "
> + "running e2fsck is recommended");
It looks like you have an extra space before the ext2_msg() here.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists