diff options
| author | Arnd Bergmann <[email protected]> | 2016-10-25 18:16:20 +0200 |
|---|---|---|
| committer | Doug Ledford <[email protected]> | 2016-12-14 12:12:53 -0500 |
| commit | e98172462f0b75ed60f3a73aa280fb29cafd450f (patch) | |
| tree | e4715f11d6423956a78763d08642fd13f0fd747d /tools/perf/scripts/python/syscall-counts-by-pid.py | |
| parent | 14ab8896f5d993c5f427504276e3c42ccb3cc354 (diff) | |
IB/mlx4: avoid a -Wmaybe-uninitialize warning
There is an old warning about mlx4_SW2HW_EQ_wrapper on x86:
ethernet/mellanox/mlx4/resource_tracker.c: In function ‘mlx4_SW2HW_EQ_wrapper’:
ethernet/mellanox/mlx4/resource_tracker.c:3071:10: error: ‘eq’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
The problem here is that gcc won't track the state of the variable
across a spin_unlock. Moving the assignment out of the lock is
safe here and avoids the warning.
Signed-off-by: Arnd Bergmann <[email protected]>
Reviewed-by: Yishai Hadas <[email protected]>
Signed-off-by: Doug Ledford <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts-by-pid.py')
0 files changed, 0 insertions, 0 deletions