From: kernel test robot <lkp@intel.com>
To: Mark Morra <MarkAlbert.Morra@amd.com>
Cc: clang-built-linux@googlegroups.com, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org, Gerrit Cr <Gerrit.Cr@amd.com>,
Leung Martin <Martin.Leung@amd.com>
Subject: [agd5f:amd-staging-drm-next 360/407] dc_link.c:undefined reference to `dc_dsc_stream_bandwidth_in_kbps'
Date: Sun, 1 Aug 2021 17:17:59 +0800 [thread overview]
Message-ID: <202108011756.LAyItDb5-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1865 bytes --]
tree: https://gitlab.freedesktop.org/agd5f/linux.git amd-staging-drm-next
head: 7403f8492395c0692833f8a7523718760b025159
commit: 429f534054bc2b5f21e8a73433f455247d48fb1d [360/407] drm/amd/display: Fixed EdidUtility build errors
config: s390-randconfig-r023-20210728 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project c49df15c278857adecd12db6bb1cdc96885f7079)
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
# install s390 cross compiling tool for clang build
# apt-get install binutils-s390x-linux-gnu
git remote add agd5f https://gitlab.freedesktop.org/agd5f/linux.git
git fetch --no-tags agd5f amd-staging-drm-next
git checkout 429f534054bc2b5f21e8a73433f455247d48fb1d
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross O=build_dir ARCH=s390 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
Note: the agd5f/amd-staging-drm-next HEAD 7403f8492395c0692833f8a7523718760b025159 builds fine.
It only hurts bisectibility.
All errors (new ones prefixed by >>):
s390x-linux-gnu-ld: drivers/gpu/drm/amd/display/dc/core/dc_link.o: in function `dc_link_allocate_mst_payload':
>> dc_link.c:(.text+0x37e6): undefined reference to `dc_dsc_stream_bandwidth_in_kbps'
s390x-linux-gnu-ld: drivers/gpu/drm/amd/display/dc/core/dc_link.o: in function `dc_bandwidth_in_kbps_from_timing':
dc_link.c:(.text+0x69b8): undefined reference to `dc_dsc_stream_bandwidth_in_kbps'
---
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: 36858 bytes --]
reply other threads:[~2021-08-01 9:18 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=202108011756.LAyItDb5-lkp@intel.com \
--to=lkp@intel.com \
--cc=Gerrit.Cr@amd.com \
--cc=MarkAlbert.Morra@amd.com \
--cc=Martin.Leung@amd.com \
--cc=clang-built-linux@googlegroups.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.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).