Be explicit in order of evaluation in the reiserfs code
authorTony Breeds <tony@bakeyournoodle.com>
Tue, 10 Feb 2009 03:11:23 +0000 (14:11 +1100)
committerTony Breeds <tony@bakeyournoodle.com>
Tue, 18 Oct 2011 04:11:10 +0000 (15:11 +1100)
commit94adb3aee138118174e34f519ff6ce3e8ece707c
tree43baf655f2e5d0c8988276f701a156db932c01e3
parentf82dc817c486c26448514b4ef82d49b34a80dd25
Be explicit in order of evaluation in the reiserfs code

GCC Has helpfully pointed out that we're doing some strange things:

second/fs_reiserfs.c: In function ‘block_read’:
second/fs_reiserfs.c:219: warning: operation on ‘journal_table’ may be undefined
second/fs_reiserfs.c:219: warning: operation on ‘journal_table’ may be undefined
second/fs_reiserfs.c:219: warning: operation on ‘journal_table’ may be undefined
second/fs_reiserfs.c: In function ‘next_key’:
second/fs_reiserfs.c:619: warning: operation on ‘depth’ may be undefined

Signed-off-by: Tony Breeds <tony@bakeyournoodle.com>
second/fs_reiserfs.c