From: kbuild test robot <lkp@intel.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: kbuild-all@lists.01.org, linux-media@vger.kernel.org
Subject: [linuxtv-media:master 454/495] drivers/staging/media/atomisp/pci/sh_css_firmware.h:41:38: warning: 'struct device' declared inside parameter list will not be visible outside of this definition or declaration
Date: Thu, 21 May 2020 03:12:27 +0800 [thread overview]
Message-ID: <202005210324.cOPl29AE%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1511 bytes --]
tree: git://linuxtv.org/media_tree.git master
head: 960b2dee908b0fc51cf670841de13b40b44aaaae
commit: 8568fe630066a733456fb1ffc8e1402191d7e27c [454/495] media: atomisp: print a better message when fw version is wrong
config: i386-allyesconfig (attached as .config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce:
git checkout 8568fe630066a733456fb1ffc8e1402191d7e27c
# save the attached .config to linux build tree
make ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All warnings (new ones prefixed by >>, old ones prefixed by <<):
In file included from drivers/staging/media/atomisp/pci/sh_css_version.c:19:0:
>> drivers/staging/media/atomisp/pci/sh_css_firmware.h:41:38: warning: 'struct device' declared inside parameter list will not be visible outside of this definition or declaration
sh_css_check_firmware_version(struct device *dev, const char *fw_data);
^~~~~~
drivers/staging/media/atomisp/pci/sh_css_firmware.h:44:29: warning: 'struct device' declared inside parameter list will not be visible outside of this definition or declaration
sh_css_load_firmware(struct device *dev, const char *fw_data,
^~~~~~
vim +41 drivers/staging/media/atomisp/pci/sh_css_firmware.h
39
40 bool
> 41 sh_css_check_firmware_version(struct device *dev, const char *fw_data);
42
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 72759 bytes --]
reply other threads:[~2020-05-20 19:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202005210324.cOPl29AE%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).