vol: nuke() doesn't need to zero code
authorSimon Wilkinson <sxw@your-file-system.com>
Tue, 19 Feb 2013 14:48:59 +0000 (14:48 +0000)
committerJeffrey Altman <jaltman@your-file-system.com>
Thu, 21 Feb 2013 17:07:19 +0000 (09:07 -0800)
We don't need to zero the result code two lines before we assign
a new value to it - just remove the pointless assignment

Caught by clang-analyzer

Change-Id: I8fefdc839ef9980d7f7703add3b11b089d524d38
Reviewed-on: http://gerrit.openafs.org/9167
Reviewed-by: Chas Williams - CONTRACTOR <chas@cmf.nrl.navy.mil>
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Derrick Brashear <shadow@your-file-system.com>
Reviewed-by: Jeffrey Altman <jaltman@your-file-system.com>

src/vol/nuke.c

index 3399de5..7679c50 100644 (file)
@@ -190,7 +190,7 @@ nuke(char *aname, VolumeId avolid)
            li = ti;
        }
        if (li) free(li);
-       code = 0;               /* we really don't care about it except for debugging */
+
        allInodes = NULL;
 
        /* at this point, we should try to remove the volume header file itself.