Re: [PATCH] drm/exynos: fix a timeout loop

2017-01-23 Thread Inki Dae
2017년 01월 23일 18:41에 Chris Wilson 이(가) 쓴 글: > On Mon, Jan 23, 2017 at 06:32:16PM +0900, Inki Dae wrote: >> >> >> 2017년 01월 21일 01:54에 Tobias Jakobi 이(가) 쓴 글: >>> From: Dan Carpenter >>> >>> We were trying to print an error message if we timed out here, but the >>> loop actually ends with "tries"

Re: [PATCH] drm/exynos: fix a timeout loop

2017-01-23 Thread Chris Wilson
On Mon, Jan 23, 2017 at 06:32:16PM +0900, Inki Dae wrote: > > > 2017년 01월 21일 01:54에 Tobias Jakobi 이(가) 쓴 글: > > From: Dan Carpenter > > > > We were trying to print an error message if we timed out here, but the > > loop actually ends with "tries" set to UINT_MAX and not zero. Fix this > > by

Re: [PATCH] drm/exynos: fix a timeout loop

2017-01-23 Thread Inki Dae
2017년 01월 21일 01:54에 Tobias Jakobi 이(가) 쓴 글: > From: Dan Carpenter > > We were trying to print an error message if we timed out here, but the > loop actually ends with "tries" set to UINT_MAX and not zero. Fix this > by changing from tries-- to --tries. Sorry but I already know this patch fro

[PATCH] drm/exynos: fix a timeout loop

2017-01-20 Thread Tobias Jakobi
From: Dan Carpenter We were trying to print an error message if we timed out here, but the loop actually ends with "tries" set to UINT_MAX and not zero. Fix this by changing from tries-- to --tries. A for loop would actually be the most natural way to do this. My fix means we only loop 99 time

[patch] drm/exynos: fix a timeout loop

2016-10-13 Thread Dan Carpenter
We were trying to print an error message if we timed out here, but the loop actually ends with "tries" set to UINT_MAX and not zero. Fix this by changing from tries-- to --tries. A for loop would actually be the most natural way to do this. My fix means we only loop 99 times instead of 100 but t

[patch] drm/exynos: fix a timeout loop

2016-10-13 Thread Tobias Jakobi
Hello Dan, sorry for the blunder! Patch looks good to me. Reviewed-by: Tobias Jakobi With best wishes, Tobias Dan Carpenter wrote: > We were trying to print an error message if we timed out here, but the > loop actually ends with "tries" set to UINT_MAX and not zero. Fix this > by changing