Btrfs: cleanup warnings from gcc 4.6 (nonbugs)
These are all the cases where a variable is set, but not read which are not bugs as far as I can see, but simply leftovers. Still needs more review. Found by gcc 4.6's new warnings Signed-off-by:Andi Kleen <ak@linux.intel.com> Cc: Chris Mason <chris.mason@oracle.com> Signed-off-by:
Andrew Morton <akpm@linux-foundation.org> Signed-off-by:
Chris Mason <chris.mason@oracle.com>
Showing
- fs/btrfs/compression.c 0 additions, 2 deletionsfs/btrfs/compression.c
- fs/btrfs/ctree.c 2 additions, 18 deletionsfs/btrfs/ctree.c
- fs/btrfs/disk-io.c 0 additions, 11 deletionsfs/btrfs/disk-io.c
- fs/btrfs/extent-tree.c 0 additions, 2 deletionsfs/btrfs/extent-tree.c
- fs/btrfs/extent_io.c 0 additions, 9 deletionsfs/btrfs/extent_io.c
- fs/btrfs/inode.c 0 additions, 14 deletionsfs/btrfs/inode.c
- fs/btrfs/ioctl.c 0 additions, 2 deletionsfs/btrfs/ioctl.c
- fs/btrfs/ordered-data.c 0 additions, 2 deletionsfs/btrfs/ordered-data.c
- fs/btrfs/root-tree.c 0 additions, 2 deletionsfs/btrfs/root-tree.c
- fs/btrfs/super.c 2 additions, 4 deletionsfs/btrfs/super.c
- fs/btrfs/tree-defrag.c 0 additions, 2 deletionsfs/btrfs/tree-defrag.c
- fs/btrfs/tree-log.c 0 additions, 15 deletionsfs/btrfs/tree-log.c
- fs/btrfs/volumes.c 0 additions, 4 deletionsfs/btrfs/volumes.c
- fs/btrfs/xattr.c 0 additions, 2 deletionsfs/btrfs/xattr.c
- fs/btrfs/zlib.c 0 additions, 5 deletionsfs/btrfs/zlib.c
Loading
Please register or sign in to comment