From: kernel test robot <lkp@intel.com>
To: John Clements <john.clements@amd.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Alex Deucher <alexander.deucher@amd.com>,
Guchun Chen <guchun.chen@amd.com>
Subject: [agd5f:drm-next 41/57] drivers/gpu/drm/amd/amdgpu/amdgpu_psp.c:503:6: warning: no previous prototype for 'release_psp_cmd_buf'
Date: Thu, 5 Aug 2021 21:06:07 +0800 [thread overview]
Message-ID: <202108052100.FATdZB3w-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1318 bytes --]
tree: https://gitlab.freedesktop.org/agd5f/linux.git drm-next
head: f5bb65b1b6213c07641c5e60c67fbcbb438705bc
commit: 908dada12cbe41ab5a218a8157631df48bded32b [41/57] drm/amdgpu: added synchronization for psp cmd buf access
config: i386-randconfig-r021-20210804 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.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 908dada12cbe41ab5a218a8157631df48bded32b
# save the attached .config to linux build tree
make W=1 ARCH=i386
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/amdgpu_psp.c:503:6: warning: no previous prototype for 'release_psp_cmd_buf' [-Wmissing-prototypes]
503 | void release_psp_cmd_buf(struct psp_context *psp)
| ^~~~~~~~~~~~~~~~~~~
vim +/release_psp_cmd_buf +503 drivers/gpu/drm/amd/amdgpu/amdgpu_psp.c
502
> 503 void release_psp_cmd_buf(struct psp_context *psp)
504 {
505 mutex_unlock(&psp->mutex);
506 }
507
---
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: 31152 bytes --]
reply other threads:[~2021-08-05 13:07 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=202108052100.FATdZB3w-lkp@intel.com \
--to=lkp@intel.com \
--cc=alexander.deucher@amd.com \
--cc=guchun.chen@amd.com \
--cc=john.clements@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