public inbox for intel-xe@lists.freedesktop.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 3/3] drm/i915/de: Implement register polling in the display code
Date: Sat, 14 Mar 2026 16:09:51 +0800	[thread overview]
Message-ID: <202603141514.jgf9tlEy-lkp@intel.com> (raw)
In-Reply-To: <20260313111028.25159-4-ville.syrjala@linux.intel.com>

Hi Ville,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-i915/for-linux-next]
[also build test WARNING on drm-tip/drm-tip next-20260311]
[cannot apply to drm-i915/for-linux-next-fixes drm-xe/drm-xe-next linus/master v7.0-rc3]
[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/Ville-Syrjala/drm-i915-de-Introduce-intel_de-c-and-move-intel_de_-read-write-8-there/20260314-004939
base:   https://gitlab.freedesktop.org/drm/i915/kernel.git for-linux-next
patch link:    https://lore.kernel.org/r/20260313111028.25159-4-ville.syrjala%40linux.intel.com
patch subject: [PATCH 3/3] drm/i915/de: Implement register polling in the display code
config: sparc64-allmodconfig (https://download.01.org/0day-ci/archive/20260314/202603141514.jgf9tlEy-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project 7d47b695929cc7f85eeb0f87d0189adc04c1c629)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260314/202603141514.jgf9tlEy-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/202603141514.jgf9tlEy-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/i915/display/intel_de.c:72:6: warning: variable 'ret' is used uninitialized whenever 'if' condition is false [-Wsometimes-uninitialized]
      72 |         if (fast_timeout_us)
         |             ^~~~~~~~~~~~~~~
   drivers/gpu/drm/i915/display/intel_de.c:77:6: note: uninitialized use occurs here
      77 |         if (ret && slow_timeout_us)
         |             ^~~
   drivers/gpu/drm/i915/display/intel_de.c:72:2: note: remove the 'if' if its condition is always true
      72 |         if (fast_timeout_us)
         |         ^~~~~~~~~~~~~~~~~~~~
      73 |                 ret = __intel_de_wait_for_register(display, reg, mask, value,
   drivers/gpu/drm/i915/display/intel_de.c:70:9: note: initialize the variable 'ret' to silence this warning
      70 |         int ret;
         |                ^
         |                 = 0
   1 warning generated.


vim +72 drivers/gpu/drm/i915/display/intel_de.c

    62	
    63	static int intel_de_wait_for_register(struct intel_display *display,
    64					      i915_reg_t reg, u32 mask, u32 value,
    65					      unsigned int fast_timeout_us,
    66					      unsigned int slow_timeout_us,
    67					      u32 (*read)(struct intel_display *display, i915_reg_t reg),
    68					      u32 *out_value, bool is_atomic)
    69	{
    70		int ret;
    71	
  > 72		if (fast_timeout_us)
    73			ret = __intel_de_wait_for_register(display, reg, mask, value,
    74							   fast_timeout_us, read,
    75							   out_value, is_atomic);
    76	
    77		if (ret && slow_timeout_us)
    78			ret = __intel_de_wait_for_register(display, reg, mask, value,
    79							   slow_timeout_us, read,
    80							   out_value, is_atomic);
    81	
    82		return ret;
    83	}
    84	

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

  parent reply	other threads:[~2026-03-14  8:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-13 11:10 [PATCH 0/3] drm/i915/de: Move register polling into display code Ville Syrjala
2026-03-13 11:10 ` [PATCH 1/3] drm/i915/de: Introduce intel_de.c and move intel_de_{read, write}8() there Ville Syrjala
2026-03-13 14:21   ` Jani Nikula
2026-03-13 11:10 ` [PATCH 2/3] drm/i915/de: Move intel_de_wait*() into intel_de.c Ville Syrjala
2026-03-13 14:21   ` Jani Nikula
2026-03-13 11:10 ` [PATCH 3/3] drm/i915/de: Implement register polling in the display code Ville Syrjala
2026-03-13 15:03   ` Jani Nikula
2026-03-17  7:52     ` Ville Syrjälä
2026-03-23  9:50     ` Ville Syrjälä
2026-03-14  8:09   ` kernel test robot [this message]
2026-03-23  9:43   ` [PATCH v2 " Ville Syrjala
2026-03-13 11:15 ` ✗ CI.checkpatch: warning for drm/i915/de: Move register polling into " Patchwork
2026-03-13 11:17 ` ✓ CI.KUnit: success " Patchwork
2026-03-13 11:51 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-14 14:29 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-03-23 10:43 ` ✗ CI.checkpatch: warning for drm/i915/de: Move register polling into display code (rev2) Patchwork
2026-03-23 10:45 ` ✓ CI.KUnit: success " Patchwork
2026-03-23 11:26 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-23 13:56 ` ✓ Xe.CI.FULL: " Patchwork

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=202603141514.jgf9tlEy-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=ville.syrjala@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox