From: kbuild test robot <lkp@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild-all@01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Manfred Spraul <manfred@colorfullife.com>,
Johannes Weiner <hannes@cmpxchg.org>
Subject: [mmotm:master 227/248] lima_gem.c:undefined reference to `vmf_insert_mixed'
Date: Sat, 6 Apr 2019 14:47:00 +0800 [thread overview]
Message-ID: <201904061457.ZCY5n0Jo%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]
Hi Andrew,
It's probably a bug fix that unveils the link errors.
tree: git://git.cmpxchg.org/linux-mmotm.git master
head: b09c000f671826e6f073a7f89b266e4ac998952b
commit: 39a08f353e1f30f7ba2e8b751a9034010a99666c [227/248] linux-next-git-rejects
config: sh-allyesconfig (attached as .config)
compiler: sh4-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 39a08f353e1f30f7ba2e8b751a9034010a99666c
# save the attached .config to linux build tree
GCC_VERSION=7.2.0 make.cross ARCH=sh
All errors (new ones prefixed by >>):
arch/sh/kernel/cpu/sh2/clock-sh7619.o:(.data+0x1c): undefined reference to `followparent_recalc'
drivers/gpu/drm/lima/lima_gem.o: In function `lima_gem_fault':
>> lima_gem.c:(.text+0x6c): undefined reference to `vmf_insert_mixed'
---
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: 51701 bytes --]
next reply other threads:[~2019-04-06 6:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-06 6:47 kbuild test robot [this message]
2019-04-07 19:08 ` [mmotm:master 227/248] lima_gem.c:undefined reference to `vmf_insert_mixed' Randy Dunlap
2019-04-08 1:30 ` Qiang Yu
2019-04-08 4:44 ` Randy Dunlap
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=201904061457.ZCY5n0Jo%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=manfred@colorfullife.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;
as well as URLs for NNTP newsgroup(s).