From: kernel test robot <lkp@intel.com>
To: "Leo (Hanghong) Ma" <hanghong.ma@amd.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org,
Alex Deucher <alexander.deucher@amd.com>,
Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Subject: [agd5f:drm-next 49/92] drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_dp.c:4457:4: error: implicit declaration of function 'DC_LOG_DP2'
Date: Sat, 20 Nov 2021 05:26:27 +0800 [thread overview]
Message-ID: <202111200516.BPfRAhyK-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3743 bytes --]
tree: https://gitlab.freedesktop.org/agd5f/linux.git drm-next
head: eaae0714f4a82df81a60c6aae74c568e8974a716
commit: 9c0dc981c97dc7a439469dff76bacf6415514496 [49/92] drm/amd/display: Reduce dmesg error to a debug print
config: riscv-randconfig-r004-20211118 (attached as .config)
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 riscv cross compiling tool for clang build
# apt-get install binutils-riscv64-linux-gnu
git remote add agd5f https://gitlab.freedesktop.org/agd5f/linux.git
git fetch --no-tags agd5f drm-next
git checkout 9c0dc981c97dc7a439469dff76bacf6415514496
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 ARCH=riscv
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 >>):
In file included from drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_dp.c:37:
In file included from drivers/gpu/drm/amd/amdgpu/../display/dc/dc_dmub_srv.h:30:
In file included from drivers/gpu/drm/amd/amdgpu/../display/dmub/dmub_srv.h:67:
drivers/gpu/drm/amd/amdgpu/../display/dmub/inc/dmub_cmd.h:2892:12: warning: variable 'temp' set but not used [-Wunused-but-set-variable]
uint64_t temp;
^
>> drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_dp.c:4457:4: error: implicit declaration of function 'DC_LOG_DP2' [-Werror,-Wimplicit-function-declaration]
DC_LOG_DP2("%s: Read LTTPR caps data failed.\n", __func__);
^
1 warning and 1 error generated.
vim +/DC_LOG_DP2 +4457 drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_dp.c
4446
4447 if (link->lttpr_mode == LTTPR_MODE_NON_TRANSPARENT || link->lttpr_mode == LTTPR_MODE_TRANSPARENT) {
4448 /* By reading LTTPR capability, RX assumes that we will enable
4449 * LTTPR extended aux timeout if LTTPR is present.
4450 */
4451 status = core_link_read_dpcd(
4452 link,
4453 DP_LT_TUNABLE_PHY_REPEATER_FIELD_DATA_STRUCTURE_REV,
4454 lttpr_dpcd_data,
4455 sizeof(lttpr_dpcd_data));
4456 if (status != DC_OK) {
> 4457 DC_LOG_DP2("%s: Read LTTPR caps data failed.\n", __func__);
4458 return false;
4459 }
4460
4461 link->dpcd_caps.lttpr_caps.revision.raw =
4462 lttpr_dpcd_data[DP_LT_TUNABLE_PHY_REPEATER_FIELD_DATA_STRUCTURE_REV -
4463 DP_LT_TUNABLE_PHY_REPEATER_FIELD_DATA_STRUCTURE_REV];
4464
4465 link->dpcd_caps.lttpr_caps.max_link_rate =
4466 lttpr_dpcd_data[DP_MAX_LINK_RATE_PHY_REPEATER -
4467 DP_LT_TUNABLE_PHY_REPEATER_FIELD_DATA_STRUCTURE_REV];
4468
4469 link->dpcd_caps.lttpr_caps.phy_repeater_cnt =
4470 lttpr_dpcd_data[DP_PHY_REPEATER_CNT -
4471 DP_LT_TUNABLE_PHY_REPEATER_FIELD_DATA_STRUCTURE_REV];
4472
4473 link->dpcd_caps.lttpr_caps.max_lane_count =
4474 lttpr_dpcd_data[DP_MAX_LANE_COUNT_PHY_REPEATER -
4475 DP_LT_TUNABLE_PHY_REPEATER_FIELD_DATA_STRUCTURE_REV];
4476
4477 link->dpcd_caps.lttpr_caps.mode =
4478 lttpr_dpcd_data[DP_PHY_REPEATER_MODE -
4479 DP_LT_TUNABLE_PHY_REPEATER_FIELD_DATA_STRUCTURE_REV];
4480
4481 link->dpcd_caps.lttpr_caps.max_ext_timeout =
4482 lttpr_dpcd_data[DP_PHY_REPEATER_EXTENDED_WAIT_TIMEOUT -
4483 DP_LT_TUNABLE_PHY_REPEATER_FIELD_DATA_STRUCTURE_REV];
4484
---
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: 34391 bytes --]
reply other threads:[~2021-11-19 21:27 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=202111200516.BPfRAhyK-lkp@intel.com \
--to=lkp@intel.com \
--cc=alexander.deucher@amd.com \
--cc=hanghong.ma@amd.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nicholas.kazlauskas@amd.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