From: kernel test robot <lkp@intel.com>
To: Matthew Auld <matthew.auld@intel.com>
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
intel-gfx@lists.freedesktop.org, kbuild-all@lists.01.org,
dri-devel@lists.freedesktop.org
Subject: [Intel-gfx] [drm-intel:drm-intel-gt-next 7/8] drivers/gpu/drm/i915/intel_region_ttm.c:181:6: error: no previous prototype for 'intel_region_ttm_node_free'
Date: Wed, 23 Jun 2021 18:04:01 +0800 [thread overview]
Message-ID: <202106231856.R1itGYXk-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1639 bytes --]
tree: git://anongit.freedesktop.org/drm-intel drm-intel-gt-next
head: 13c2ceb6addb6b14468e09b75832c98909eed8e7
commit: d53ec322dc7de32a59bf1c2a56b93e90fc2f1c28 [7/8] drm/i915/ttm: switch over to ttm_buddy_man
config: i386-defconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
git remote add drm-intel git://anongit.freedesktop.org/drm-intel
git fetch --no-tags drm-intel drm-intel-gt-next
git checkout d53ec322dc7de32a59bf1c2a56b93e90fc2f1c28
# save the attached .config to linux build tree
make W=1 ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
Note: the drm-intel/drm-intel-gt-next HEAD ca319ee9ca6a6ef95143df8d0a57b2941c2a9566 builds fine.
It only hurts bisectibility.
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/i915/intel_region_ttm.c:181:6: error: no previous prototype for 'intel_region_ttm_node_free' [-Werror=missing-prototypes]
181 | void intel_region_ttm_node_free(struct intel_memory_region *mem,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
vim +/intel_region_ttm_node_free +181 drivers/gpu/drm/i915/intel_region_ttm.c
180
> 181 void intel_region_ttm_node_free(struct intel_memory_region *mem,
182 struct ttm_resource *res)
183 {
184 struct ttm_resource_manager *man = mem->region_private;
185
186 man->func->free(man, res);
187 }
188
---
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: 29242 bytes --]
[-- Attachment #3: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
reply other threads:[~2021-06-23 10:05 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=202106231856.R1itGYXk-lkp@intel.com \
--to=lkp@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kbuild-all@lists.01.org \
--cc=matthew.auld@intel.com \
--cc=thomas.hellstrom@linux.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