diff options
| author | Arnd Bergmann <[email protected]> | 2016-01-25 16:54:04 +0100 |
|---|---|---|
| committer | Stephen Boyd <[email protected]> | 2016-01-29 17:20:08 -0800 |
| commit | 9849fadfc07eeb2a3699f1ccb7b61f59d2c3c6b8 (patch) | |
| tree | 1e3295181d2f54596913719f097b848340fc05bd /tools/perf/scripts/python | |
| parent | 3d6f1c7212d0823cbc056b1c184c7fe0cfef553a (diff) | |
clk: st: avoid uninitialized variable use
My previous patch fixed some warnings about printing a couple
of variables that are always uninitialized in quadfs_pll_fs660c32_set_rate(),
but I now got a warning that only shows up in some configurations (i.e.
without gcc -Os) about the params.ndiv being used uninitialized in the
error case:
drivers/clk/st/clkgen-fsyn.c: In function 'quadfs_pll_fs660c32_set_rate':
drivers/clk/st/clkgen-fsyn.c:584:75: warning: 'params.ndiv' may be used uninitialized in this function [-Wmaybe-uninitialized]
drivers/clk/st/clkgen-fsyn.c:574:16: note: 'params.ndiv' was declared here
This changes the error handling so we bail for invalid arguments rather
than continuing with uninitialized data.
Signed-off-by: Arnd Bergmann <[email protected]>
Signed-off-by: Stephen Boyd <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions