From: kernel test robot <lkp@intel.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Richard Weinberger <richard@nod.at>
Subject: [linux-next:master 12108/15421] ERROR: modpost: "X86_FEATURE_XMM" [drivers/misc/altera-stapl/altera-stapl.ko] undefined!
Date: Fri, 30 Apr 2021 04:30:55 +0800 [thread overview]
Message-ID: <202104300449.w2UON4hm-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1329 bytes --]
Hi Randy,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 9e5cff2a1315fec1da1f497714395670366506b6
commit: a730af6e3114d549555f4b130c216bad1c3aa80e [12108/15421] um: Add 2 missing libs to fix various build errors
config: um-randconfig-r025-20210429 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=a730af6e3114d549555f4b130c216bad1c3aa80e
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout a730af6e3114d549555f4b130c216bad1c3aa80e
# save the attached .config to linux build tree
make W=1 W=1 ARCH=um
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 >>, old ones prefixed by <<):
>> ERROR: modpost: "X86_FEATURE_XMM" [drivers/misc/altera-stapl/altera-stapl.ko] undefined!
>> ERROR: modpost: "X86_FEATURE_XMM2" [drivers/misc/altera-stapl/altera-stapl.ko] undefined!
---
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: 12980 bytes --]
reply other threads:[~2021-04-29 20:39 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=202104300449.w2UON4hm-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=rdunlap@infradead.org \
--cc=richard@nod.at \
/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