| commit | 797f91e6417abcc9a07f9c99dd9128ae7622ee81 | |
| author | Hans de Goede <hdegoede@redhat.com> | |
| Sun, 28 May 2017 12:31:48 +0000 (28 09:31 -0300) | ||
| committer | Mauro Carvalho Chehab <mchehab@s-opensource.com> | |
| Wed, 7 Jun 2017 15:47:17 +0000 (7 12:47 -0300) | ||
| tree | 66dfcfeaf5c3e0aafa52d6c8ff263d8c2967d13b | treesnapshot (tar.gz zip) |
| parent | 008d8e10054b3548cf9781083c26809486d7c07c | commitdiff |
[media] staging: atomisp: Do not call dev_warn with a NULL device
Do not call dev_warn with a NULL device, this silence the following 2
warnings:
[ 14.392194] (NULL device *): Failed to find gmin variable gmin_V2P8GPIO
[ 14.392257] (NULL device *): Failed to find gmin variable gmin_V1P8GPIO
We could switch to using pr_warn for dev == NULL instead, but as comments
in the source indicate, the check for these 2 special gmin variables with
a NULL device is a workaround for 2 specific evaluation boards, so
completely silencing the missing warning for these actually is a good
thing.
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Do not call dev_warn with a NULL device, this silence the following 2
warnings:
[ 14.392194] (NULL device *): Failed to find gmin variable gmin_V2P8GPIO
[ 14.392257] (NULL device *): Failed to find gmin variable gmin_V1P8GPIO
We could switch to using pr_warn for dev == NULL instead, but as comments
in the source indicate, the check for these 2 special gmin variables with
a NULL device is a workaround for 2 specific evaluation boards, so
completely silencing the missing warning for these actually is a good
thing.
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
| drivers/staging/media/atomisp/platform/intel-mid/atomisp_gmin_platform.c | diffblobblamehistory |