From: kernel test robot <lkp@intel.com>
To: Icenowy Zheng <uwu@icenowy.me>
Cc: oe-kbuild-all@lists.linux.dev, dri-devel@lists.freedesktop.org,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: [drm-misc:drm-misc-next 3/5] drivers/gpu/drm/verisilicon/vs_bridge.c:325:9-16: WARNING: ERR_CAST can be used with bridge
Date: Tue, 24 Feb 2026 21:03:29 +0800 [thread overview]
Message-ID: <202602242000.bQ0qN6AC-lkp@intel.com> (raw)
tree: https://gitlab.freedesktop.org/drm/misc/kernel.git drm-misc-next
head: 61c0f69a2ff79c8f388a9e973abb4853be467127
commit: dbf21777caa8b8c88c12f7f036b01208fec0d55a [3/5] drm: verisilicon: add a driver for Verisilicon display controllers
config: riscv-randconfig-r052-20260224 (https://download.01.org/0day-ci/archive/20260224/202602242000.bQ0qN6AC-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project 9a109fbb6e184ec9bcce10615949f598f4c974a9)
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/202602242000.bQ0qN6AC-lkp@intel.com/
cocci warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/verisilicon/vs_bridge.c:325:9-16: WARNING: ERR_CAST can be used with bridge
--
>> drivers/gpu/drm/verisilicon/vs_crtc.c:175:9-16: WARNING: ERR_CAST can be used with primary
--
>> drivers/gpu/drm/verisilicon/vs_dc.c:109:2-9: line 109 is redundant because platform_get_irq() already prints an error
vim +325 drivers/gpu/drm/verisilicon/vs_bridge.c
288
289 struct vs_bridge *vs_bridge_init(struct drm_device *drm_dev,
290 struct vs_crtc *crtc)
291 {
292 unsigned int output = crtc->id;
293 struct vs_bridge *bridge;
294 struct drm_bridge *next;
295 enum vs_bridge_output_interface intf;
296 const struct drm_bridge_funcs *bridge_funcs;
297 int ret, enctype;
298
299 intf = vs_bridge_detect_output_interface(drm_dev->dev->of_node,
300 output);
301 if (intf == -ENODEV) {
302 drm_dbg(drm_dev, "Skipping output %u\n", output);
303 return NULL;
304 }
305
306 next = devm_drm_of_get_bridge(drm_dev->dev, drm_dev->dev->of_node,
307 output, intf);
308 if (IS_ERR(next)) {
309 ret = PTR_ERR(next);
310 if (ret != -EPROBE_DEFER)
311 drm_err(drm_dev,
312 "Cannot get downstream bridge of output %u\n",
313 output);
314 return ERR_PTR(ret);
315 }
316
317 if (intf == VSDC_OUTPUT_INTERFACE_DPI)
318 bridge_funcs = &vs_dpi_bridge_funcs;
319 else
320 bridge_funcs = &vs_dp_bridge_funcs;
321
322 bridge = devm_drm_bridge_alloc(drm_dev->dev, struct vs_bridge, base,
323 bridge_funcs);
324 if (IS_ERR(bridge))
> 325 return ERR_PTR(PTR_ERR(bridge));
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-02-24 13: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=202602242000.bQ0qN6AC-lkp@intel.com \
--to=lkp@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tzimmermann@suse.de \
--cc=uwu@icenowy.me \
/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.