From: kernel test robot <lkp@intel.com>
To: Matthew Auld <matthew.auld@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
"Linux Memory Management List" <linux-mm@kvack.org>,
"Christian König" <christian.koenig@amd.com>,
"Arunpravin Paneer Selvam" <Arunpravin.PaneerSelvam@amd.com>
Subject: [linux-next:pending-fixes 326/436] xtensa-linux-ld: drivers/gpu/drm/tests/drm_buddy_test.o:undefined reference to `__umoddi3'
Date: Fri, 16 Feb 2024 12:00:03 +0800 [thread overview]
Message-ID: <202402161104.YJ096OVa-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git pending-fixes
head: a8f5f47b9dc3b207e4d0f7bfcc893907a5047d59
commit: a64056bb5a3215bd31c8ce17d609ba0f4d5c55ea [326/436] drm/tests/drm_buddy: add alloc_contiguous test
config: xtensa-randconfig-002-20240215 (https://download.01.org/0day-ci/archive/20240216/202402161104.YJ096OVa-lkp@intel.com/config)
compiler: xtensa-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240216/202402161104.YJ096OVa-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/202402161104.YJ096OVa-lkp@intel.com/
All errors (new ones prefixed by >>):
>> xtensa-linux-ld: drivers/gpu/drm/tests/drm_buddy_test.o:(.text+0x6c): undefined reference to `__umoddi3'
xtensa-linux-ld: drivers/gpu/drm/tests/drm_buddy_test.o: in function `drm_test_buddy_alloc_contiguous':
drm_buddy_test.c:(.text+0x166): undefined reference to `__umoddi3'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-02-16 6:09 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=202402161104.YJ096OVa-lkp@intel.com \
--to=lkp@intel.com \
--cc=Arunpravin.PaneerSelvam@amd.com \
--cc=christian.koenig@amd.com \
--cc=linux-mm@kvack.org \
--cc=matthew.auld@intel.com \
--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