diff options
| author |   Jiri Olsa <jolsa@kernel.org> | 2017-09-08 14:05:07 +0200 |
|---|---|---|
| committer |   Arnaldo Carvalho de Melo <acme@redhat.com> | 2017-09-12 12:34:46 -0300 |
| commit | 4d286c89e412fc2eaa1b8988481d2f32b5e3826f (patch) | |
| tree | 84bbfd172257b0a4fb79f798d193627eb7ccd7bb /block | |
| parent | perf tools: Open perf.data with O_CLOEXEC flag (diff) | |
| download | linux-dev-4d286c89e412fc2eaa1b8988481d2f32b5e3826f.tar.xz linux-dev-4d286c89e412fc2eaa1b8988481d2f32b5e3826f.zip | |
perf ui progress: Make sure we always define step value
Unlikely, but we could have ui_progress__init being called with total <
16, which would set the next and step variables to 0. That would force
unnecessary ui_progress__ops->update calls because 'next' would never
raise.
Forcing the next and step values to be always > 0.
Signed-off-by: Jiri Olsa <jolsa@kernel.org>
Cc: David Ahern <dsahern@gmail.com>
Cc: Namhyung Kim <namhyung@kernel.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Link: http://lkml.kernel.org/r/20170908120510.22515-2-jolsa@kernel.org
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions