The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Zhi Wang <zhi.a.wang@intel.com>
Cc: kbuild-all@lists.01.org, zhenyu.z.wang@intel.com,
	terrence.xu@intel.com, intel-gvt-dev@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
	Zhenyu Wang <zhenyuw@linux.intel.com>
Subject: [intel-gvt:gvt-next-bak-2022-04-13 2/4] drivers/gpu/drm/i915/intel_gvt.h:66:5: error: no previous prototype for 'intel_gvt_iterate_mmio_table'
Date: Wed, 20 Apr 2022 14:06:58 +0800	[thread overview]
Message-ID: <202204201327.wDSzH3pV-lkp@intel.com> (raw)

tree:   https://github.com/intel/gvt-linux.git gvt-next-bak-2022-04-13
head:   f267d34e47f33a283b785a31b7b8d1c899502743
commit: e870ce1791520cd03f67c5a16f309d94e4aede85 [2/4] i915/gvt: Separate the MMIO tracking table from GVT-g
config: i386-defconfig (https://download.01.org/0day-ci/archive/20220420/202204201327.wDSzH3pV-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.2.0-20) 11.2.0
reproduce (this is a W=1 build):
        # https://github.com/intel/gvt-linux/commit/e870ce1791520cd03f67c5a16f309d94e4aede85
        git remote add intel-gvt https://github.com/intel/gvt-linux.git
        git fetch --no-tags intel-gvt gvt-next-bak-2022-04-13
        git checkout e870ce1791520cd03f67c5a16f309d94e4aede85
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        make W=1 O=build_dir ARCH=i386 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 >>):

   In file included from drivers/gpu/drm/i915/gvt/gvt.h:39,
                    from drivers/gpu/drm/i915/gvt/mpt.h:36,
                    from <command-line>:
   drivers/gpu/drm/i915/intel_gvt.h:66:41: error: 'struct intel_gvt_mmio_table_iter' declared inside parameter list will not be visible outside of this definition or declaration [-Werror]
      66 | int intel_gvt_iterate_mmio_table(struct intel_gvt_mmio_table_iter *iter)
         |                                         ^~~~~~~~~~~~~~~~~~~~~~~~~
>> drivers/gpu/drm/i915/intel_gvt.h:66:5: error: no previous prototype for 'intel_gvt_iterate_mmio_table' [-Werror=missing-prototypes]
      66 | int intel_gvt_iterate_mmio_table(struct intel_gvt_mmio_table_iter *iter)
         |     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
   cc1: all warnings being treated as errors


vim +/intel_gvt_iterate_mmio_table +66 drivers/gpu/drm/i915/intel_gvt.h

    65	
  > 66	int intel_gvt_iterate_mmio_table(struct intel_gvt_mmio_table_iter *iter)
    67	{
    68		return 0;
    69	}
    70	#endif
    71	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

             reply	other threads:[~2022-04-20  6:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-20  6:06 kernel test robot [this message]
2022-04-20  7:03 ` [intel-gvt:gvt-next-bak-2022-04-13 2/4] drivers/gpu/drm/i915/intel_gvt.h:66:5: error: no previous prototype for 'intel_gvt_iterate_mmio_table' Christoph Hellwig

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=202204201327.wDSzH3pV-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=hch@lst.de \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=terrence.xu@intel.com \
    --cc=zhenyu.z.wang@intel.com \
    --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