From: kernel test robot <lkp@intel.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Stephen Boyd <swboyd@chromium.org>,
Abhinav Kumar <quic_abhinavk@quicinc.com>
Subject: [drm-msm:msm-next-staging 7/32] drivers/gpu/drm/msm/msm_drv.c:236:17: error: implicit declaration of function 'drm_bridge_remove'; did you mean 'drm_bridge_detach'?
Date: Sat, 30 Apr 2022 18:36:25 +0800 [thread overview]
Message-ID: <202204301804.hJxOQfse-lkp@intel.com> (raw)
tree: https://gitlab.freedesktop.org/drm/msm.git msm-next-staging
head: d2dc68276133362f021bc8d429433b5818826c81
commit: d28ea556267c4f2ec7264ab49f1b1296834321ec [7/32] drm/msm: properly add and remove internal bridges
config: parisc-randconfig-r023-20220428 (https://download.01.org/0day-ci/archive/20220430/202204301804.hJxOQfse-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 11.3.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 drm-msm https://gitlab.freedesktop.org/drm/msm.git
git fetch --no-tags drm-msm msm-next-staging
git checkout d28ea556267c4f2ec7264ab49f1b1296834321ec
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=parisc SHELL=/bin/bash drivers/gpu/drm/msm/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
drivers/gpu/drm/msm/msm_drv.c: In function 'msm_drm_uninit':
>> drivers/gpu/drm/msm/msm_drv.c:236:17: error: implicit declaration of function 'drm_bridge_remove'; did you mean 'drm_bridge_detach'? [-Werror=implicit-function-declaration]
236 | drm_bridge_remove(priv->bridges[i]);
| ^~~~~~~~~~~~~~~~~
| drm_bridge_detach
cc1: some warnings being treated as errors
vim +236 drivers/gpu/drm/msm/msm_drv.c
230
231 msm_disp_snapshot_destroy(ddev);
232
233 drm_mode_config_cleanup(ddev);
234
235 for (i = 0; i < priv->num_bridges; i++)
> 236 drm_bridge_remove(priv->bridges[i]);
237
238 pm_runtime_get_sync(dev);
239 msm_irq_uninstall(ddev);
240 pm_runtime_put_sync(dev);
241
242 if (kms && kms->funcs)
243 kms->funcs->destroy(kms);
244
245 if (priv->vram.paddr) {
246 unsigned long attrs = DMA_ATTR_NO_KERNEL_MAPPING;
247 drm_mm_takedown(&priv->vram.mm);
248 dma_free_attrs(dev, priv->vram.size, NULL,
249 priv->vram.paddr, attrs);
250 }
251
252 component_unbind_all(dev, ddev);
253
254 ddev->dev_private = NULL;
255 drm_dev_put(ddev);
256
257 destroy_workqueue(priv->wq);
258
259 return 0;
260 }
261
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-04-30 10:36 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=202204301804.hJxOQfse-lkp@intel.com \
--to=lkp@intel.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=swboyd@chromium.org \
/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
all inboxes | Powered by JetHome®