diff options
| author | Jean Delvare <khali@linux-fr.org> | 2013-03-31 07:16:37 -0300 |
|---|---|---|
| committer | Mauro Carvalho Chehab <mchehab@redhat.com> | 2013-03-31 11:15:35 -0300 |
| commit | b0efc3ed0530b08e9e1cba5f63e9c251ca3d7428 (patch) | |
| tree | be2da07dd482f359c8a53ab593f10522d1ac55a7 /arch/m32r/Kconfig | |
| parent | 46f85978687152c53a69fc06951e386f194e7f5d (diff) | |
| download | linux-3.10-b0efc3ed0530b08e9e1cba5f63e9c251ca3d7428.tar.gz linux-3.10-b0efc3ed0530b08e9e1cba5f63e9c251ca3d7428.tar.bz2 linux-3.10-b0efc3ed0530b08e9e1cba5f63e9c251ca3d7428.zip | |
[media] m920x: Fix uninitialized variable warning
drivers/media/usb/dvb-usb/m920x.c:91:6: warning: "ret" may be used uninitialized in this function [-Wuninitialized]
drivers/media/usb/dvb-usb/m920x.c:70:6: note: "ret" was declared here
This is real, if a remote control has an empty initialization sequence
we would get success or failure randomly.
OTOH the initialization of ret in m920x_init is needless, the function
returns with an error as soon as an error happens, so the last return
can only be a success and we can hard-code 0 there.
Signed-off-by: Jean Delvare <khali@linux-fr.org>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'arch/m32r/Kconfig')
0 files changed, 0 insertions, 0 deletions