public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Dillon Varone <Dillon.Varone@amd.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	Alex Deucher <alexander.deucher@amd.com>,
	Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>,
	Fangzhi Zuo <jerry.zuo@amd.com>
Subject: drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_srv.c:862 dmub_srv_fb_cmd_execute() warn: inconsistent indenting
Date: Tue, 24 Mar 2026 17:07:45 +0800	[thread overview]
Message-ID: <202603241709.34oBV0zd-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   c369299895a591d96745d6492d4888259b004a9e
commit: a3b7dc4a1ec4e184f48c2f8205d2ec88d31310fe drm/amd/display: Add Support for reg inbox0 for host->DMUB CMDs
date:   12 months ago
config: x86_64-randconfig-r073-20260323 (https://download.01.org/0day-ci/archive/20260324/202603241709.34oBV0zd-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
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/202603241709.34oBV0zd-lkp@intel.com/

New smatch warnings:
drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_srv.c:862 dmub_srv_fb_cmd_execute() warn: inconsistent indenting

Old smatch warnings:
drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_srv.c:961 dmub_srv_wait_for_pending() warn: inconsistent indenting
drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_srv.c:994 dmub_srv_wait_for_idle() warn: inconsistent indenting

vim +862 drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_srv.c

   842	
   843	enum dmub_status dmub_srv_fb_cmd_execute(struct dmub_srv *dmub)
   844	{
   845		struct dmub_rb flush_rb;
   846	
   847		if (!dmub->hw_init)
   848			return DMUB_STATUS_INVALID;
   849	
   850		if (dmub->power_state != DMUB_POWER_STATE_D0)
   851			return DMUB_STATUS_POWER_STATE_D3;
   852	
   853		/**
   854		 * Read back all the queued commands to ensure that they've
   855		 * been flushed to framebuffer memory. Otherwise DMCUB might
   856		 * read back stale, fully invalid or partially invalid data.
   857		 */
   858		flush_rb = dmub->inbox1.rb;
   859		flush_rb.rptr = dmub->inbox1_last_wptr;
   860		dmub_rb_flush_pending(&flush_rb);
   861	
 > 862			dmub->hw_funcs.set_inbox1_wptr(dmub, dmub->inbox1.rb.wrpt);
   863	
   864		dmub->inbox1_last_wptr = dmub->inbox1.rb.wrpt;
   865	
   866		return DMUB_STATUS_OK;
   867	}
   868	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

             reply	other threads:[~2026-03-24  9:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-24  9:07 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-12-16 23:52 drivers/gpu/drm/amd/amdgpu/../display/dmub/src/dmub_srv.c:862 dmub_srv_fb_cmd_execute() warn: inconsistent indenting 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=202603241709.34oBV0zd-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Dillon.Varone@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=jerry.zuo@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicholas.kazlauskas@amd.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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