diff options
| author | Eric Sandeen <sandeen@redhat.com> | 2014-02-20 13:32:10 -0500 |
|---|---|---|
| committer | Theodore Ts'o <tytso@mit.edu> | 2014-02-20 13:32:10 -0500 |
| commit | dc9ddd984df5f5611c7e2149d19be5a8721c1ac5 (patch) | |
| tree | 529e27a9059cff932de90b11e558cca38bfd0e38 /drivers/memory | |
| parent | e861b5e9a47bd8c6a7491a2b9f6e9a230b1b8e86 (diff) | |
| download | op-kernel-dev-dc9ddd984df5f5611c7e2149d19be5a8721c1ac5.zip op-kernel-dev-dc9ddd984df5f5611c7e2149d19be5a8721c1ac5.tar.gz | |
ext4: remove unused ac_ex_scanned
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@redhat.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Diffstat (limited to 'drivers/memory')
0 files changed, 0 insertions, 0 deletions
