From: kernel test robot <lkp@intel.com>
To: Matthew Auld <matthew.auld@intel.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Nirmoy Das <nirmoy.das@intel.com>
Subject: [linux-next:master 9649/10678] i915_scatterlist.c:undefined reference to `__udivdi3'
Date: Fri, 15 Jul 2022 00:11:06 +0800 [thread overview]
Message-ID: <202207150007.pINMWSAK-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 37b355fdaf31ee18bda9a93c2a438dc1cbf57ec9
commit: aff1e0b09b54b64944b7fe32997229552737b9e9 [9649/10678] drm/i915/ttm: fix sg_table construction
config: i386-defconfig (https://download.01.org/0day-ci/archive/20220715/202207150007.pINMWSAK-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=aff1e0b09b54b64944b7fe32997229552737b9e9
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 aff1e0b09b54b64944b7fe32997229552737b9e9
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
Note: the linux-next/master HEAD 37b355fdaf31ee18bda9a93c2a438dc1cbf57ec9 builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
ld: drivers/gpu/drm/i915/i915_scatterlist.o: in function `i915_rsgt_from_mm_node':
>> i915_scatterlist.c:(.text+0x196): undefined reference to `__udivdi3'
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-07-14 16:11 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=202207150007.pINMWSAK-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=matthew.auld@intel.com \
--cc=nirmoy.das@intel.com \
--cc=rodrigo.vivi@intel.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