aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/bin
diff options
context:
space:
mode:
authorArnd Bergmann <[email protected]>2018-03-13 14:05:16 +0100
committerGreg Kroah-Hartman <[email protected]>2018-03-14 12:56:15 +0100
commitae91ce5db517626168a970806e650122a9b6d9f7 (patch)
treead0a8947b0470d7010b37a4c5fd78bd0a38d01db /tools/perf/scripts/python/bin
parent7a76eaf41a545fad34f17ea36da41b5e7df38616 (diff)
staging: lustre: fid: avoid false-positive uninitialized variable warning
One of Neil's recent cleanups apparently has led the code to get to a state where gcc tracks the 'seqnr' variable just enough to see that it is sometimes initialized in seq_client_alloc_seq(), but not enough that it can prove this initialization to be reliable before the use of that variable: drivers/staging/lustre/lustre/fid/fid_request.c: In function 'seq_client_alloc_fid': drivers/staging/lustre/lustre/fid/fid_request.c:245:22: error: 'seqnr' may be used uninitialized in this function [-Werror=maybe-uninitialized] The code seems to be otherwise correct, and I could not come up with a good way to simplify it further, so this adds a fake initialization to shut up that warning. Signed-off-by: Arnd Bergmann <[email protected]> Reviewed-by: NeilBrown <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions