From: kernel test robot <lkp@intel.com>
To: Zhi Wang <zhi.a.wang@intel.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Christoph Hellwig <hch@lst.de>,
Zhenyu Wang <zhenyuw@linux.intel.com>
Subject: [linux-next:master 4790/7959] drivers/gpu/drm/i915/gvt/handlers.c:74:6: error: no previous prototype for 'intel_gvt_match_device'
Date: Sat, 30 Apr 2022 22:59:29 +0800 [thread overview]
Message-ID: <202204302238.gbu0m6qN-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 5469f0c06732a077c70a759a81f2a1f00b277694
commit: e0f74ed4634d6d662e7dca19115d0da1143a3ec0 [4790/7959] i915/gvt: Separate the MMIO tracking table from GVT-g
config: x86_64-rhel-8.3-syz (https://download.01.org/0day-ci/archive/20220430/202204302238.gbu0m6qN-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.2.0-20) 11.2.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=e0f74ed4634d6d662e7dca19115d0da1143a3ec0
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout e0f74ed4634d6d662e7dca19115d0da1143a3ec0
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/gpu/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/i915/gvt/handlers.c:74:6: error: no previous prototype for 'intel_gvt_match_device' [-Werror=missing-prototypes]
74 | bool intel_gvt_match_device(struct intel_gvt *gvt,
| ^~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
vim +/intel_gvt_match_device +74 drivers/gpu/drm/i915/gvt/handlers.c
12d14cc43b3470 Zhi Wang 2016-08-30 73
12d14cc43b3470 Zhi Wang 2016-08-30 @74 bool intel_gvt_match_device(struct intel_gvt *gvt,
12d14cc43b3470 Zhi Wang 2016-08-30 75 unsigned long device)
12d14cc43b3470 Zhi Wang 2016-08-30 76 {
12d14cc43b3470 Zhi Wang 2016-08-30 77 return intel_gvt_get_device_type(gvt) & device;
12d14cc43b3470 Zhi Wang 2016-08-30 78 }
12d14cc43b3470 Zhi Wang 2016-08-30 79
:::::: The code at line 74 was first introduced by commit
:::::: 12d14cc43b34706283246917329b2182163ba9aa drm/i915/gvt: Introduce a framework for tracking HW registers.
:::::: TO: Zhi Wang <zhi.a.wang@intel.com>
:::::: CC: Zhenyu Wang <zhenyuw@linux.intel.com>
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-04-30 15:00 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=202204302238.gbu0m6qN-lkp@intel.com \
--to=lkp@intel.com \
--cc=hch@lst.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=zhenyuw@linux.intel.com \
--cc=zhi.a.wang@intel.com \
/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