From: kernel test robot <lkp@intel.com>
To: Alex Sierra <alex.sierra@amd.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Alex Deucher <alexander.deucher@amd.com>,
Philip Yang <Philip.Yang@amd.com>,
Felix Kuehling <Felix.Kuehling@amd.com>
Subject: [linux-next:master 3829/8441] drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_svm.c:50:9: error: implicit declaration of function '_dynamic_func_call_no_desc'
Date: Sat, 12 Aug 2023 04:33:04 +0800 [thread overview]
Message-ID: <202308120420.43Ww4zyU-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 21ef7b1e17d039053edaeaf41142423810572741
commit: 8923137dbe4b24863694c35284df51d036b5dd5e [3829/8441] drm/amdkfd: avoid svm dump when dynamic debug disabled
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20230812/202308120420.43Ww4zyU-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce: (https://download.01.org/0day-ci/archive/20230812/202308120420.43Ww4zyU-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202308120420.43Ww4zyU-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_svm.c: In function 'svm_range_set_attr':
>> drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_svm.c:50:9: error: implicit declaration of function '_dynamic_func_call_no_desc' [-Werror=implicit-function-declaration]
50 | _dynamic_func_call_no_desc("svm_range_dump", svm_range_debug_dump, svms)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_svm.c:3568:9: note: in expansion of macro 'dynamic_svm_range_dump'
3568 | dynamic_svm_range_dump(svms);
| ^~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/_dynamic_func_call_no_desc +50 drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_svm.c
44
45 /* Long enough to ensure no retry fault comes after svm range is restored and
46 * page table is updated.
47 */
48 #define AMDGPU_SVM_RANGE_RETRY_FAULT_PENDING (2UL * NSEC_PER_MSEC)
49 #define dynamic_svm_range_dump(svms) \
> 50 _dynamic_func_call_no_desc("svm_range_dump", svm_range_debug_dump, svms)
51
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-08-11 20:33 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=202308120420.43Ww4zyU-lkp@intel.com \
--to=lkp@intel.com \
--cc=Felix.Kuehling@amd.com \
--cc=Philip.Yang@amd.com \
--cc=alex.sierra@amd.com \
--cc=alexander.deucher@amd.com \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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