From: kernel test robot <lkp@intel.com>
To: Sonny Jiang <sonjiang@amd.com>
Cc: oe-kbuild-all@lists.linux.dev,
Alex Deucher <alexander.deucher@amd.com>,
Leo Liu <leo.liu@amd.com>
Subject: [linux-next:master 6581/7246] drivers/gpu/drm/amd/amdgpu/jpeg_v5_0_2.c:274 jpeg_v5_0_2_hw_fini() warn: inconsistent indenting
Date: Thu, 19 Mar 2026 09:03:46 +0800 [thread overview]
Message-ID: <202603190931.mQLtG2LC-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 8e42d2514a7e8eb8d740d0ba82339dd6c0b6463f
commit: 855e3e19f69c0133a98dfae3ec9d26089cd50e77 [6581/7246] drm/amdgpu: Add JPEG_v5_0_2 IP block
config: i386-randconfig-141-20260319 (https://download.01.org/0day-ci/archive/20260319/202603190931.mQLtG2LC-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
smatch: v0.5.0-9004-gb810ac53
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/202603190931.mQLtG2LC-lkp@intel.com/
smatch warnings:
drivers/gpu/drm/amd/amdgpu/jpeg_v5_0_2.c:274 jpeg_v5_0_2_hw_fini() warn: inconsistent indenting
vim +274 drivers/gpu/drm/amd/amdgpu/jpeg_v5_0_2.c
259
260 /**
261 * jpeg_v5_0_2_hw_fini - stop the hardware block
262 *
263 * @ip_block: Pointer to the amdgpu_ip_block for this hw instance.
264 *
265 * Stop the JPEG block, mark ring as not ready any more
266 */
267 static int jpeg_v5_0_2_hw_fini(struct amdgpu_ip_block *ip_block)
268 {
269 struct amdgpu_device *adev = ip_block->adev;
270 int ret = 0;
271
272 cancel_delayed_work_sync(&adev->jpeg.idle_work);
273
> 274 if (adev->jpeg.cur_state != AMD_PG_STATE_GATE)
275 ret = jpeg_v5_0_2_set_powergating_state(ip_block, AMD_PG_STATE_GATE);
276
277 return ret;
278 }
279
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-19 1:04 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=202603190931.mQLtG2LC-lkp@intel.com \
--to=lkp@intel.com \
--cc=alexander.deucher@amd.com \
--cc=leo.liu@amd.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sonjiang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.