From: kernel test robot <lkp@intel.com>
To: Andre Jun Hirata <andrejhirata@usp.br>,
kenneth.feng@amd.com, alexander.deucher@amd.com,
christian.koenig@amd.com, airlied@gmail.com, simona@ffwll.ch
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
gabriel.dimant@usp.br, guilhermesangabriel@usp.br,
Andre Jun Hirata <andrejhirata@usp.br>
Subject: Re: [PATCH v5] drm/amd/pm: Use guard(mutex) instead of manual lock+unlock
Date: Wed, 13 May 2026 08:12:04 +0200 [thread overview]
Message-ID: <202605130808.IJrao3wX-lkp@intel.com> (raw)
In-Reply-To: <20260508230312.6108-1-andrejhirata@usp.br>
Hi Andre,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-misc/drm-misc-next]
[also build test ERROR on next-20260508]
[cannot apply to linus/master v6.16-rc1]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Andre-Jun-Hirata/drm-amd-pm-Use-guard-mutex-instead-of-manual-lock-unlock/20260513-040937
base: https://gitlab.freedesktop.org/drm/misc/kernel.git drm-misc-next
patch link: https://lore.kernel.org/r/20260508230312.6108-1-andrejhirata%40usp.br
patch subject: [PATCH v5] drm/amd/pm: Use guard(mutex) instead of manual lock+unlock
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20260513/202605130808.IJrao3wX-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260513/202605130808.IJrao3wX-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202605130808.IJrao3wX-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/amd/amdgpu/../pm/amdgpu_dpm.c:247:40: error: expected ';' after return statement
247 | return smu_mode1_reset_is_support(smu)
| ^
| ;
drivers/gpu/drm/amd/amdgpu/../pm/amdgpu_dpm.c:833:24: warning: unused variable 'vstate' [-Wunused-variable]
833 | struct amd_vce_state *vstate = NULL;
| ^~~~~~
1 warning and 1 error generated.
vim +247 drivers/gpu/drm/amd/amdgpu/../pm/amdgpu_dpm.c
238
239 bool amdgpu_dpm_is_mode1_reset_supported(struct amdgpu_device *adev)
240 {
241 struct smu_context *smu = adev->powerplay.pp_handle;
242
243 if (!is_support_sw_smu(adev))
244 return false;
245
246 guard(mutex)(&adev->pm.mutex);
> 247 return smu_mode1_reset_is_support(smu)
248 }
249
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-05-13 6:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 2:47 [PATCH RESEND] drm/amd/pm: Use guard(mutex) instead of manual lock+unlock Andre Hirata
2026-05-08 8:43 ` Christian König
2026-05-08 10:36 ` Andre Jun Hirata
2026-05-08 11:12 ` [PATCH v2] " Andre Jun Hirata
2026-05-08 12:44 ` Christian König
2026-05-08 14:21 ` [PATCH v3] " Andre Jun Hirata
2026-05-08 17:23 ` [PATCH v4] " Andre Jun Hirata
2026-05-08 23:03 ` [PATCH v5] " Andre Jun Hirata
2026-05-11 4:58 ` Wang, Yang(Kevin)
2026-05-11 12:42 ` [PATCH v6] " Andre Jun Hirata
2026-05-11 13:50 ` Lazar, Lijo
2026-05-12 23:04 ` [PATCH v7] " Andre Jun Hirata
2026-05-13 5:38 ` [PATCH v8] " Andre Jun Hirata
2026-05-13 4:39 ` [PATCH v5] " kernel test robot
2026-05-13 6:12 ` kernel test robot [this message]
2026-05-13 5:11 ` [PATCH v4] " kernel test robot
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=202605130808.IJrao3wX-lkp@intel.com \
--to=lkp@intel.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=andrejhirata@usp.br \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gabriel.dimant@usp.br \
--cc=guilhermesangabriel@usp.br \
--cc=kenneth.feng@amd.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=simona@ffwll.ch \
/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