On Mon, Jul 29, 2013 at 06:14:03PM -0500, Eric Sandeen wrote: > When looking at a bug report with: > > > kernel: EXT4-fs: 0 scanned, 0 found > > I thought wow, 0 scanned, that's odd? But it's not odd; it's printing > a variable that is initialized to 0 and never touched again. > > It's never been used since the original merge, so I don't really even > know what the original intent was, either. > > If anyone knows how to hook it up, speak now via patch, otherwise just > yank it so it's not making a confusing situation more confusing in > kernel logs. > > Signed-off-by: Eric Sandeen <sandeen@xxxxxxxxxx> Sorry for losing track of this patch. Since Andreas was sitting next to me at FAST, when I was going through the patchwork backlog, I conferred with him, and he agreed that we should just nuke ac_ex_scanned as you proposed. Thanks, applied. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html