Jiri Olsa 4d286c89e4 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>		2017-09-12 12:34:46 -03:00
..
accounting
arch	tools headers: Sync cpu features kernel ABI headers with tooling headers	2017-08-28 16:44:46 -03:00
build	tools build tests: Don't hardcode gcc name	2017-08-28 16:44:44 -03:00
cgroup
firewire
gpio
hv
iio
include	tools include linux: Guard against redefinition of some macros	2017-09-12 12:33:39 -03:00
kvm/kvm_stat
laptop
leds
lib	tools lib api: Fix make DEBUG=1 build	2017-09-12 12:34:14 -03:00
net
nfsd
objtool	objtool: Handle GCC stack pointer adjustment bug	2017-08-30 10:48:41 +02:00
pci
pcmcia
perf	perf ui progress: Make sure we always define step value	2017-09-12 12:34:46 -03:00
power
scripts	perf tools: Robustify detection of clang binary	2017-08-28 16:44:46 -03:00
spi
testing	Merge branch 'timers-core-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip	2017-09-04 13:06:34 -07:00
thermal/tmon
time
usb
virtio
vm
Makefile