From: kernel test robot <lkp@intel.com>
To: Angus Wang <Angus.Wang@amd.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Alex Deucher <alexander.deucher@amd.com>,
Anthony Koo <Anthony.Koo@amd.com>, Aric Cyr <Aric.Cyr@amd.com>
Subject: [linux-next:master 2009/2869] freesync.c:undefined reference to `__aeabi_uldivmod'
Date: Thu, 7 Apr 2022 20:31:07 +0800 [thread overview]
Message-ID: <202204072006.j865p2gY-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 109f6d10ec17302c4666f7df3dfa0e31d8589d41
commit: 3fe5739db488434bc0368577615ea7275b0f43a5 [2009/2869] drm/amd/display: Add flip interval workaround
config: arm-allyesconfig (https://download.01.org/0day-ci/archive/20220407/202204072006.j865p2gY-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=3fe5739db488434bc0368577615ea7275b0f43a5
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 3fe5739db488434bc0368577615ea7275b0f43a5
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arm SHELL=/bin/bash
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 >>):
arm-linux-gnueabi-ld: drivers/gpu/drm/amd/display/modules/freesync/freesync.o: in function `mod_freesync_handle_v_update':
>> freesync.c:(.text+0x26c4): undefined reference to `__aeabi_uldivmod'
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-04-07 12:32 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=202204072006.j865p2gY-lkp@intel.com \
--to=lkp@intel.com \
--cc=Angus.Wang@amd.com \
--cc=Anthony.Koo@amd.com \
--cc=Aric.Cyr@amd.com \
--cc=alexander.deucher@amd.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
/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).