1. 19 Jul, 2017 16 commits
  2. 18 Jul, 2017 21 commits
  3. 17 Jul, 2017 3 commits
    • Javier Martinez Canillas's avatar
      media: vimc: set id_table for platform drivers · bb3abbb7
      Javier Martinez Canillas authored
      The vimc platform drivers define a platform device ID table but these
      are not set to the .id_table field in the platform driver structure.
      
      So the platform device ID table is only used to fill the aliases in
      the module but are not used for matching (works because the platform
      subsystem fallbacks to the driver's name if no .id_table is set).
      
      But this also means that the platform device ID table isn't used if
      the driver is built-in, which leads to the following build warning:
      
      This causes the following build warnings when the driver is built-in:
      
      drivers/media/platform/vimc//vimc-capture.c:528:40: warning: ‘vimc_cap_driver_ids’ defined but not used [-Wunused-const-variable=]
       static const struct platform_device_id vimc_cap_driver_ids[] = {
                                              ^~~~~~~~~~~~~~~~~~~
      drivers/media/platform/vimc//vimc-debayer.c:588:40: warning: ‘vimc_deb_driver_ids’ defined but not used [-Wunused-const-variable=]
       static const struct platform_device_id vimc_deb_driver_ids[] = {
                                              ^~~~~~~~~~~~~~~~~~~
      drivers/media/platform/vimc//vimc-scaler.c:442:40: warning: ‘vimc_sca_driver_ids’ defined but not used [-Wunused-const-variable=]
       static const struct platform_device_id vimc_sca_driver_ids[] = {
                                              ^~~~~~~~~~~~~~~~~~~
      drivers/media/platform/vimc//vimc-sensor.c:376:40: warning: ‘vimc_sen_driver_ids’ defined but not used [-Wunused-const-variable=]
       static const struct platform_device_id vimc_sen_driver_ids[] = {
                                              ^~~~~~~~~~~~~~~~~~~
      Reported-by: default avatarMauro Carvalho Chehab <mchehab@s-opensource.com>
      Suggested-by: default avatarSakari Ailus <sakari.ailus@iki.fi>
      Signed-off-by: default avatarJavier Martinez Canillas <javierm@redhat.com>
      Reviewed-by: default avatarHelen Koike <helen.koike@collabora.com>
      Acked-by: default avatarSakari Ailus <sakari.ailus@linux.intel.com>
      bb3abbb7
    • Mauro Carvalho Chehab's avatar
      media: staging: atomisp: disable warnings with cc-disable-warning · a1a0a56f
      Mauro Carvalho Chehab authored
      Instead of directly using -Wno-foo, use cc-disable-warning, as it
      checks if the compiler has the warnings we want to disable.
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@s-opensource.com>
      a1a0a56f
    • Mauro Carvalho Chehab's avatar
      media: davinci: variable 'common' set but not used · 9a01968c
      Mauro Carvalho Chehab authored
      Get rid of those two warnings:
      drivers/media/platform/davinci/vpif_capture.c: In function 'vpif_remove':
      drivers/media/platform/davinci/vpif_capture.c:1722:21: warning: variable 'common' set but not used [-Wunused-but-set-variable]
        struct common_obj *common;
                           ^~~~~~
      drivers/media/platform/davinci/vpif_display.c: In function 'vpif_remove':
      drivers/media/platform/davinci/vpif_display.c:1342:21: warning: variable 'common' set but not used [-Wunused-but-set-variable]
        struct common_obj *common;
                           ^~~~~~
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@s-opensource.com>
      9a01968c