From: kernel test robot <lkp@intel.com>
To: Becle Lee <becle.lee@amd.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Alex Deucher <alexander.deucher@amd.com>,
Hersen Wu <hersenxs.wu@amd.com>, Aric Cyr <Aric.Cyr@amd.com>
Subject: [agd5f:drm-next 48/65] drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_hubp.c:1319:6: warning: no previous prototype for 'hubp1_wait_pipe_read_start'
Date: Wed, 16 Mar 2022 23:00:26 +0800 [thread overview]
Message-ID: <202203162243.lsr37uYW-lkp@intel.com> (raw)
tree: https://gitlab.freedesktop.org/agd5f/linux.git drm-next
head: 426c89aa203bcec9d9cf6eea36735eafa1b1f099
commit: dd15640bcee5a5fa74fc52557dd6220f48b01116 [48/65] drm/amd/display: Wait for hubp read line for Pollock
config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20220316/202203162243.lsr37uYW-lkp@intel.com/config)
compiler: gcc-9 (Ubuntu 9.4.0-1ubuntu1~20.04) 9.4.0
reproduce (this is a W=1 build):
git remote add agd5f https://gitlab.freedesktop.org/agd5f/linux.git
git fetch --no-tags agd5f drm-next
git checkout dd15640bcee5a5fa74fc52557dd6220f48b01116
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash drivers/gpu/drm/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_hubp.c:1319:6: warning: no previous prototype for 'hubp1_wait_pipe_read_start' [-Wmissing-prototypes]
1319 | void hubp1_wait_pipe_read_start(struct hubp *hubp)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/hubp1_wait_pipe_read_start +1319 drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_hubp.c
1313
1314 /**
1315 * hubp1_wait_pipe_read_start - wait for hubp ret path starting read.
1316 *
1317 * @hubp: hubp struct reference.
1318 */
> 1319 void hubp1_wait_pipe_read_start(struct hubp *hubp)
1320 {
1321 struct dcn10_hubp *hubp1 = TO_DCN10_HUBP(hubp);
1322
1323 REG_WAIT(HUBPRET_READ_LINE_STATUS,
1324 PIPE_READ_VBLANK, 0,
1325 1, 1000);
1326 }
1327
---
0-DAY CI Kernel Test Service
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-03-16 15:03 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=202203162243.lsr37uYW-lkp@intel.com \
--to=lkp@intel.com \
--cc=Aric.Cyr@amd.com \
--cc=alexander.deucher@amd.com \
--cc=becle.lee@amd.com \
--cc=hersenxs.wu@amd.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
all inboxes | Powered by JetHome®