diff options
| author | Arnd Bergmann <[email protected]> | 2017-02-28 18:14:37 -0300 |
|---|---|---|
| committer | Mauro Carvalho Chehab <[email protected]> | 2017-03-22 10:12:54 -0300 |
| commit | 27430d19a91615245babaa9b216d0807636903a0 (patch) | |
| tree | ef3bc5418480a6c3e8d8729d89740316a7b5f0ac /tools/perf/scripts/python | |
| parent | c3d173a396c2700cb1ba02744fdc112f461f8177 (diff) | |
[media] tw5864: use dev_warn instead of WARN to shut up warning
tw5864_frameinterval_get() only initializes its output when it successfully
identifies the video standard in tw5864_input. We get a warning here because
gcc can't always track the state if initialized warnings across a WARN()
macro, and thinks it might get used incorrectly in tw5864_s_parm:
media/pci/tw5864/tw5864-video.c: In function 'tw5864_s_parm':
media/pci/tw5864/tw5864-video.c:816:38: error: 'time_base.numerator' may be used uninitialized in this function [-Werror=maybe-uninitialized]
media/pci/tw5864/tw5864-video.c:819:31: error: 'time_base.denominator' may be used uninitialized in this function [-Werror=maybe-uninitialized]
Using dev_warn() instead of WARN() avoids the __branch_check__() in
unlikely and lets the compiler see that the initialization is correct.
Signed-off-by: Arnd Bergmann <[email protected]>
Acked-by: Andrey Utkin <[email protected]>
Signed-off-by: Hans Verkuil <[email protected]>
Signed-off-by: Mauro Carvalho Chehab <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions