From: kernel test robot <lkp@intel.com>
To: Mike Galbraith <umgwanakikbuti@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Thomas Gleixner <tglx@linutronix.de>
Subject: [rt-devel:linux-6.8.y-rt 63/96] drivers/gpu/drm/i915/display/intel_vblank.c:284:16: warning: assignment to 'long unsigned int' from 'void *' makes integer from pointer without a cast
Date: Sat, 27 Jan 2024 22:09:42 +0800 [thread overview]
Message-ID: <202401272258.allUAzSx-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git linux-6.8.y-rt
head: ff2361c71bd48a300cf147f5ffa6cd0f67135879
commit: 722e48bb3059ead4fcf48804b314d165a7609029 [63/96] drm/i915: Use preempt_disable/enable_rt() where recommended
config: loongarch-allmodconfig (https://download.01.org/0day-ci/archive/20240127/202401272258.allUAzSx-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240127/202401272258.allUAzSx-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/202401272258.allUAzSx-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/gpu/drm/i915/display/intel_vblank.c: In function 'intel_vblank_section_enter_irqsave':
>> drivers/gpu/drm/i915/display/intel_vblank.c:284:16: warning: assignment to 'long unsigned int' from 'void *' makes integer from pointer without a cast [-Wint-conversion]
284 | *flags = NULL;
| ^
drivers/gpu/drm/i915/display/intel_vblank.c: In function 'intel_vblank_section_exit_irqrestore':
>> drivers/gpu/drm/i915/display/intel_vblank.c:295:17: warning: suggest braces around empty body in an 'if' statement [-Wempty-body]
295 | ;
| ^
vim +284 drivers/gpu/drm/i915/display/intel_vblank.c
267
268 /*
269 * The uncore version of the spin lock functions is used to decide
270 * whether we need to lock the uncore lock or not. This is only
271 * needed in i915, not in Xe.
272 *
273 * This lock in i915 is needed because some old platforms (at least
274 * IVB and possibly HSW as well), which are not supported in Xe, need
275 * all register accesses to the same cacheline to be serialized,
276 * otherwise they may hang.
277 */
278 static void intel_vblank_section_enter_irqsave(struct drm_i915_private *i915, unsigned long *flags)
279 __acquires(i915->uncore.lock)
280 {
281 #ifdef I915
282 spin_lock_irqsave(&i915->uncore.lock, *flags);
283 #else
> 284 *flags = NULL;
285 #endif
286 }
287
288 static void intel_vblank_section_exit_irqrestore(struct drm_i915_private *i915, unsigned long flags)
289 __releases(i915->uncore.lock)
290 {
291 #ifdef I915
292 spin_unlock_irqrestore(&i915->uncore.lock, flags);
293 #else
294 if (flags)
> 295 ;
296 #endif
297 }
298 static void intel_vblank_section_enter(struct drm_i915_private *i915)
299 __acquires(i915->uncore.lock)
300 {
301 #ifdef I915
302 spin_lock(&i915->uncore.lock);
303 #endif
304 }
305
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-01-27 14:10 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=202401272258.allUAzSx-lkp@intel.com \
--to=lkp@intel.com \
--cc=bigeasy@linutronix.de \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tglx@linutronix.de \
--cc=umgwanakikbuti@gmail.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.