All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Luca Ceresoli <luca.ceresoli@bootlin.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [linux-next:master 10241/12559] drivers/gpu/drm/verisilicon/vs_bridge.c:306:7: warning: assignment to 'struct drm_bridge *' from 'int' makes pointer from integer without a cast
Date: Thu, 01 Oct 2026 00:07:10 +0200	[thread overview]
Message-ID: <202609302316.aEF8QlMC-lkp@intel.com> (raw)

Hi Luca,

FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   6c2cb8b8b843d216ab549b678a0d8831c43153e0
commit: aa8a8c7e4641ebcef02dd6fa387ca334857367f4 [10241/12559] drm/bridge: panel: move all code to drm_panel.c
config: xtensa-randconfig-r2307-20260930 (https://download.01.org/0day-ci/archive/20260930/202609302316.aEF8QlMC-lkp@intel.com/config)
compiler: xtensa-linux-gcc (GCC) 8.5.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260930/202609302316.aEF8QlMC-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/202609302316.aEF8QlMC-lkp@intel.com/

All warnings (new ones prefixed by >>):

   drivers/gpu/drm/verisilicon/vs_bridge.c: In function 'vs_bridge_init':
   drivers/gpu/drm/verisilicon/vs_bridge.c:306:9: error: implicit declaration of function 'devm_drm_of_get_bridge'; did you mean 'devm_drm_put_bridge'? [-Werror=implicit-function-declaration]
     next = devm_drm_of_get_bridge(drm_dev->dev, drm_dev->dev->of_node,
            ^~~~~~~~~~~~~~~~~~~~~~
            devm_drm_put_bridge
>> drivers/gpu/drm/verisilicon/vs_bridge.c:306:7: warning: assignment to 'struct drm_bridge *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
     next = devm_drm_of_get_bridge(drm_dev->dev, drm_dev->dev->of_node,
          ^
   cc1: some warnings being treated as errors


vim +306 drivers/gpu/drm/verisilicon/vs_bridge.c

dbf21777caa8b8 Icenowy Zheng 2026-01-29  288  
dbf21777caa8b8 Icenowy Zheng 2026-01-29  289  struct vs_bridge *vs_bridge_init(struct drm_device *drm_dev,
dbf21777caa8b8 Icenowy Zheng 2026-01-29  290  				 struct vs_crtc *crtc)
dbf21777caa8b8 Icenowy Zheng 2026-01-29  291  {
dbf21777caa8b8 Icenowy Zheng 2026-01-29  292  	unsigned int output = crtc->id;
dbf21777caa8b8 Icenowy Zheng 2026-01-29  293  	struct vs_bridge *bridge;
dbf21777caa8b8 Icenowy Zheng 2026-01-29  294  	struct drm_bridge *next;
dbf21777caa8b8 Icenowy Zheng 2026-01-29  295  	enum vs_bridge_output_interface intf;
dbf21777caa8b8 Icenowy Zheng 2026-01-29  296  	const struct drm_bridge_funcs *bridge_funcs;
dbf21777caa8b8 Icenowy Zheng 2026-01-29  297  	int ret, enctype;
dbf21777caa8b8 Icenowy Zheng 2026-01-29  298  
dbf21777caa8b8 Icenowy Zheng 2026-01-29  299  	intf = vs_bridge_detect_output_interface(drm_dev->dev->of_node,
dbf21777caa8b8 Icenowy Zheng 2026-01-29  300  						 output);
dbf21777caa8b8 Icenowy Zheng 2026-01-29  301  	if (intf == -ENODEV) {
dbf21777caa8b8 Icenowy Zheng 2026-01-29  302  		drm_dbg(drm_dev, "Skipping output %u\n", output);
dbf21777caa8b8 Icenowy Zheng 2026-01-29  303  		return NULL;
dbf21777caa8b8 Icenowy Zheng 2026-01-29  304  	}
dbf21777caa8b8 Icenowy Zheng 2026-01-29  305  
dbf21777caa8b8 Icenowy Zheng 2026-01-29 @306  	next = devm_drm_of_get_bridge(drm_dev->dev, drm_dev->dev->of_node,

:::::: The code at line 306 was first introduced by commit
:::::: dbf21777caa8b8c88c12f7f036b01208fec0d55a drm: verisilicon: add a driver for Verisilicon display controllers

:::::: TO: Icenowy Zheng <uwu@icenowy.me>
:::::: CC: Thomas Zimmermann <tzimmermann@suse.de>

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

                 reply	other threads:[~2026-09-30 22:07 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=202609302316.aEF8QlMC-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=luca.ceresoli@bootlin.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 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.