From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [mripard:rpi4-misc-hdmi 83/95] drivers/gpu/drm/ingenic/ingenic-drm.c:558:20: error: initialization of 'void drm_crtc struct drm_atomic_state from incompatible pointer type 'void drm_crtc struct drm_crtc_state
Date: Tue, 28 Jul 2020 01:17:43 +0800 [thread overview]
Message-ID: <202007280139.b4Ti4aOg%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3032 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git rpi4-misc-hdmi
head: d9154e8b1d283f3076232d956128cd0ddf8a032e
commit: 1620e2fb25396ff0f8a971960ce2df22cc6620ff [83/95] drm/atomic: Pass the full state to CRTC enable/disable
config: mips-gcw0_defconfig (attached as .config)
compiler: mipsel-linux-gcc (GCC) 9.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 checkout 1620e2fb25396ff0f8a971960ce2df22cc6620ff
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=mips
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/ingenic/ingenic-drm.c:558:20: error: initialization of 'void (*)(struct drm_crtc *, struct drm_atomic_state *)' from incompatible pointer type 'void (*)(struct drm_crtc *, struct drm_crtc_state *)' [-Werror=incompatible-pointer-types]
558 | .atomic_enable = ingenic_drm_crtc_atomic_enable,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/gpu/drm/ingenic/ingenic-drm.c:558:20: note: (near initialization for 'ingenic_drm_crtc_helper_funcs.atomic_enable')
drivers/gpu/drm/ingenic/ingenic-drm.c:559:21: error: initialization of 'void (*)(struct drm_crtc *, struct drm_atomic_state *)' from incompatible pointer type 'void (*)(struct drm_crtc *, struct drm_crtc_state *)' [-Werror=incompatible-pointer-types]
559 | .atomic_disable = ingenic_drm_crtc_atomic_disable,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/gpu/drm/ingenic/ingenic-drm.c:559:21: note: (near initialization for 'ingenic_drm_crtc_helper_funcs.atomic_disable')
cc1: some warnings being treated as errors
vim +558 drivers/gpu/drm/ingenic/ingenic-drm.c
90b86fcc47b4d1 Paul Cercueil 2019-06-03 556
90b86fcc47b4d1 Paul Cercueil 2019-06-03 557 static const struct drm_crtc_helper_funcs ingenic_drm_crtc_helper_funcs = {
90b86fcc47b4d1 Paul Cercueil 2019-06-03 @558 .atomic_enable = ingenic_drm_crtc_atomic_enable,
90b86fcc47b4d1 Paul Cercueil 2019-06-03 559 .atomic_disable = ingenic_drm_crtc_atomic_disable,
90b86fcc47b4d1 Paul Cercueil 2019-06-03 560 .atomic_flush = ingenic_drm_crtc_atomic_flush,
90b86fcc47b4d1 Paul Cercueil 2019-06-03 561 .atomic_check = ingenic_drm_crtc_atomic_check,
90b86fcc47b4d1 Paul Cercueil 2019-06-03 562 };
90b86fcc47b4d1 Paul Cercueil 2019-06-03 563
:::::: The code at line 558 was first introduced by commit
:::::: 90b86fcc47b4d186f92cd66393fe51871615b4cc DRM: Add KMS driver for the Ingenic JZ47xx SoCs
:::::: TO: Paul Cercueil <paul@crapouillou.net>
:::::: CC: Sam Ravnborg <sam@ravnborg.org>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 23810 bytes --]
reply other threads:[~2020-07-27 17:17 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=202007280139.b4Ti4aOg%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.