From: kbuild test robot <lkp@intel.com>
To: Shirish S <shirish.s@amd.com>
Cc: Gerrit Cr <Gerrit.Cr@amd.com>, Rex Zhu <Rex.Zhu@amd.com>,
kbuild-all@01.org, dri-devel@lists.freedesktop.org
Subject: [radeon-alex:amd-staging-drm-next 709/711] drivers/gpu/drm/amd/amdgpu/../powerplay/smumgr/smu8_smumgr.c:76:3: error: 'val' undeclared
Date: Sun, 28 Oct 2018 00:34:42 +0800 [thread overview]
Message-ID: <201810280040.hIRUZkJz%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2376 bytes --]
tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-drm-next
head: af1ad4786a34698ea5bc7a3e6fb833646b22c71d
commit: 97a7445714f44d2a978237281af297b299770f16 [709/711] drm/amdgpu: fix reporting of failed msg sent to SMU
config: i386-randconfig-j2-10212027 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
git checkout 97a7445714f44d2a978237281af297b299770f16
# save the attached .config to linux build tree
make ARCH=i386
Note: the radeon-alex/amd-staging-drm-next HEAD af1ad4786a34698ea5bc7a3e6fb833646b22c71d builds fine.
It only hurts bisectibility.
All errors (new ones prefixed by >>):
drivers/gpu/drm/amd/amdgpu/../powerplay/smumgr/smu8_smumgr.c: In function 'smu8_send_msg_to_smc_async':
drivers/gpu/drm/amd/amdgpu/../powerplay/smumgr/smu8_smumgr.c:67:11: error: expected identifier or '(' before '=' token
uint32_t = val;
^
>> drivers/gpu/drm/amd/amdgpu/../powerplay/smumgr/smu8_smumgr.c:76:3: error: 'val' undeclared (first use in this function)
val = cgs_read_register(hwmgr->device,
^
drivers/gpu/drm/amd/amdgpu/../powerplay/smumgr/smu8_smumgr.c:76:3: note: each undeclared identifier is reported only once for each function it appears in
vim +/val +76 drivers/gpu/drm/amd/amdgpu/../powerplay/smumgr/smu8_smumgr.c
63
64 static int smu8_send_msg_to_smc_async(struct pp_hwmgr *hwmgr, uint16_t msg)
65 {
66 int result = 0;
> 67 uint32_t = val;
68
69 if (hwmgr == NULL || hwmgr->device == NULL)
70 return -EINVAL;
71
72 result = PHM_WAIT_FIELD_UNEQUAL(hwmgr,
73 SMU_MP1_SRBM2P_RESP_0, CONTENT, 0);
74 if (result != 0) {
75 /* Read the last message to SMU, to report actual cause */
> 76 val = cgs_read_register(hwmgr->device,
77 mmSMU_MP1_SRBM2P_MSG_0);
78 pr_err("smu8_send_msg_to_smc_async (0x%04x) failed\n", msg);
79 pr_err("SMU still servicing msg (0x%04x)\n", val);
80 return result;
81 }
82
83 cgs_write_register(hwmgr->device, mmSMU_MP1_SRBM2P_RESP_0, 0);
84 cgs_write_register(hwmgr->device, mmSMU_MP1_SRBM2P_MSG_0, msg);
85
86 return 0;
87 }
88
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 30599 bytes --]
[-- Attachment #3: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
reply other threads:[~2018-10-27 16:34 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=201810280040.hIRUZkJz%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=Gerrit.Cr@amd.com \
--cc=Rex.Zhu@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kbuild-all@01.org \
--cc=shirish.s@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;
as well as URLs for NNTP newsgroup(s).