From: kbuild test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@linux.ibm.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: [rcu:dev.2019.03.27a 35/46] drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c:45: undefined reference to `kfd_processes_srcu'
Date: Fri, 29 Mar 2019 05:51:36 +0800 [thread overview]
Message-ID: <201903290533.Cy39CvTk%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1446 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2019.03.27a
head: 3833875fa13a3f442252a48784a18f27879a4551
commit: 016b9910f5db3d900066a0c3a8b42855f70bb1cf [35/46] drivers/gpu/drm/amd: Dynamically allocate kfd_processes_srcu
config: i386-randconfig-m1-201912 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
git checkout 016b9910f5db3d900066a0c3a8b42855f70bb1cf
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.o: In function `amdgpu_amdkfd_init':
>> drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c:45: undefined reference to `kfd_processes_srcu'
drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.o: In function `amdgpu_amdkfd_fini':
drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c:64: undefined reference to `kfd_processes_srcu'
vim +45 drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c
39
40 int amdgpu_amdkfd_init(void)
41 {
42 struct sysinfo si;
43 int ret;
44
> 45 ret = init_srcu_struct(&kfd_processes_srcu);
46 WARN_ON(ret);
47 si_meminfo(&si);
48 amdgpu_amdkfd_total_mem_size = si.totalram - si.totalhigh;
49 amdgpu_amdkfd_total_mem_size *= si.mem_unit;
50
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 31610 bytes --]
reply other threads:[~2019-03-28 21:52 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=201903290533.Cy39CvTk%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.ibm.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
all inboxes | Powered by JetHome®