diff options
| author | Maxim Korotkov <korotkov.maxim.s@gmail.com> | 2023-03-22 19:28:43 +0300 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2023-03-23 21:49:15 -0700 |
| commit | 4691720f509ae037a3b2b33d008abfd8bb8ed505 (patch) | |
| tree | d79125b37f67d90c7cf3758cca51accc94ec6af0 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | 0c04328ccf8550f29f1357ae90ce460e9568a5a9 (diff) | |
bnx2: remove deadcode in bnx2_init_cpus()
The load_cpu_fw function has no error return code
and always returns zero. Checking the value returned by
this function does not make sense.
Now checking the value of the return value is misleading when reading
the code. Path with error handling was deleted in 57579f7629a3
("bnx2: Use request_firmware()").
As a result, bnx2_init_cpus() will also return only zero
Therefore, it will be safe to change the type of functions
to void and remove checking to improving readability.
Found by Security Code and Linux Verification
Center (linuxtesting.org) with SVACE
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
Signed-off-by: Maxim Korotkov <korotkov.maxim.s@gmail.com>
Link: https://lore.kernel.org/r/20230322162843.3452-1-korotkov.maxim.s@gmail.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions