public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Maxime Ripard <maxime@cerno.tech>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Dave Stevenson <dave.stevenson@raspberrypi.com>
Subject: [kraxel:drm-qemu-next 31/70] drivers/gpu/drm/vc4/vc4_dpi.c:247:18: error: implicit declaration of function 'drmm_of_get_bridge'; did you mean 'devm_drm_of_get_bridge'?
Date: Mon, 18 Jul 2022 00:43:47 +0800	[thread overview]
Message-ID: <202207180030.CoXPUpOx-lkp@intel.com> (raw)

tree:   git://git.kraxel.org/linux drm-qemu-next
head:   887ddf3251928dc39bfc58c5c62083d38a633c14
commit: 055af0235aef8110a1c44f5fc04c5c206e9e58fb [31/70] drm/vc4: dpi: Switch to drmm_of_get_bridge
config: mips-randconfig-r025-20220717 (https://download.01.org/0day-ci/archive/20220718/202207180030.CoXPUpOx-lkp@intel.com/config)
compiler: mipsel-linux-gcc (GCC) 12.1.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        git remote add kraxel git://git.kraxel.org/linux
        git fetch --no-tags kraxel drm-qemu-next
        git checkout 055af0235aef8110a1c44f5fc04c5c206e9e58fb
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=mips SHELL=/bin/bash drivers/gpu/drm/vc4/

If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>

All error/warnings (new ones prefixed by >>):

   drivers/gpu/drm/vc4/vc4_dpi.c: In function 'vc4_dpi_init_bridge':
>> drivers/gpu/drm/vc4/vc4_dpi.c:247:18: error: implicit declaration of function 'drmm_of_get_bridge'; did you mean 'devm_drm_of_get_bridge'? [-Werror=implicit-function-declaration]
     247 |         bridge = drmm_of_get_bridge(drm, dev->of_node, 0, 0);
         |                  ^~~~~~~~~~~~~~~~~~
         |                  devm_drm_of_get_bridge
>> drivers/gpu/drm/vc4/vc4_dpi.c:247:16: warning: assignment to 'struct drm_bridge *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
     247 |         bridge = drmm_of_get_bridge(drm, dev->of_node, 0, 0);
         |                ^
   cc1: some warnings being treated as errors


vim +247 drivers/gpu/drm/vc4/vc4_dpi.c

   237	
   238	/* Sets up the next link in the display chain, whether it's a panel or
   239	 * a bridge.
   240	 */
   241	static int vc4_dpi_init_bridge(struct vc4_dpi *dpi)
   242	{
   243		struct drm_device *drm = dpi->encoder.base.dev;
   244		struct device *dev = &dpi->pdev->dev;
   245		struct drm_bridge *bridge;
   246	
 > 247		bridge = drmm_of_get_bridge(drm, dev->of_node, 0, 0);
   248		if (IS_ERR(bridge)) {
   249			/* If nothing was connected in the DT, that's not an
   250			 * error.
   251			 */
   252			if (PTR_ERR(bridge) == -ENODEV)
   253				return 0;
   254			else
   255				return PTR_ERR(bridge);
   256		}
   257	
   258		return drm_bridge_attach(&dpi->encoder.base, bridge, NULL, 0);
   259	}
   260	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

                 reply	other threads:[~2022-07-17 16:44 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=202207180030.CoXPUpOx-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime@cerno.tech \
    /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