From: kernel test robot <[email protected]>
To: Kuogee Hsieh <[email protected]>
Cc: [email protected],
GNU/Weeb Mailing List <[email protected]>,
[email protected], Sasha Levin <[email protected]>,
Abhinav Kumar <[email protected]>,
Rob Clark <[email protected]>
Subject: [ammarfaizi2-block:stable/linux-stable-rc/queue/5.15 150/161] drivers/gpu/drm/msm/dp/dp_drm.c:209:25: warning: excess elements in struct initializer
Date: Sat, 9 Jul 2022 08:13:18 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
tree: https://github.com/ammarfaizi2/linux-block stable/linux-stable-rc/queue/5.15
head: ab88938c957f2e2edc60e19ab6df7830fc1c6914
commit: 17570fbfe787716e607a5496dd44312eab6e733e [150/161] drm/msm/dp: employ bridge mechanism for display enable and disable
config: arm-defconfig (https://download.01.org/0day-ci/archive/20220709/[email protected]/config)
compiler: arm-linux-gnueabi-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
# https://github.com/ammarfaizi2/linux-block/commit/17570fbfe787716e607a5496dd44312eab6e733e
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block stable/linux-stable-rc/queue/5.15
git checkout 17570fbfe787716e607a5496dd44312eab6e733e
# 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=arm SHELL=/bin/bash drivers/gpu/drm/msm/ drivers/irqchip/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <[email protected]>
All warnings (new ones prefixed by >>):
drivers/gpu/drm/msm/dp/dp_drm.c:16:27: error: field 'bridge' has incomplete type
16 | struct drm_bridge bridge;
| ^~~~~~
drivers/gpu/drm/msm/dp/dp_drm.c: In function 'dp_bridge_mode_set':
drivers/gpu/drm/msm/dp/dp_drm.c:181:55: error: invalid use of undefined type 'struct drm_bridge'
181 | msm_dp_display_mode_set(dp_display, drm_bridge->encoder, mode, adjusted_mode);
| ^~
drivers/gpu/drm/msm/dp/dp_drm.c: In function 'dp_bridge_enable':
drivers/gpu/drm/msm/dp/dp_drm.c:189:53: error: invalid use of undefined type 'struct drm_bridge'
189 | msm_dp_display_enable(dp_display, drm_bridge->encoder);
| ^~
drivers/gpu/drm/msm/dp/dp_drm.c: In function 'dp_bridge_disable':
drivers/gpu/drm/msm/dp/dp_drm.c:197:58: error: invalid use of undefined type 'struct drm_bridge'
197 | msm_dp_display_pre_disable(dp_display, drm_bridge->encoder);
| ^~
drivers/gpu/drm/msm/dp/dp_drm.c: In function 'dp_bridge_post_disable':
drivers/gpu/drm/msm/dp/dp_drm.c:205:54: error: invalid use of undefined type 'struct drm_bridge'
205 | msm_dp_display_disable(dp_display, drm_bridge->encoder);
| ^~
drivers/gpu/drm/msm/dp/dp_drm.c: At top level:
drivers/gpu/drm/msm/dp/dp_drm.c:208:21: error: variable 'dp_bridge_ops' has initializer but incomplete type
208 | static const struct drm_bridge_funcs dp_bridge_ops = {
| ^~~~~~~~~~~~~~~~
drivers/gpu/drm/msm/dp/dp_drm.c:209:10: error: 'const struct drm_bridge_funcs' has no member named 'enable'
209 | .enable = dp_bridge_enable,
| ^~~~~~
>> drivers/gpu/drm/msm/dp/dp_drm.c:209:25: warning: excess elements in struct initializer
209 | .enable = dp_bridge_enable,
| ^~~~~~~~~~~~~~~~
drivers/gpu/drm/msm/dp/dp_drm.c:209:25: note: (near initialization for 'dp_bridge_ops')
drivers/gpu/drm/msm/dp/dp_drm.c:210:10: error: 'const struct drm_bridge_funcs' has no member named 'disable'
210 | .disable = dp_bridge_disable,
| ^~~~~~~
drivers/gpu/drm/msm/dp/dp_drm.c:210:25: warning: excess elements in struct initializer
210 | .disable = dp_bridge_disable,
| ^~~~~~~~~~~~~~~~~
drivers/gpu/drm/msm/dp/dp_drm.c:210:25: note: (near initialization for 'dp_bridge_ops')
drivers/gpu/drm/msm/dp/dp_drm.c:211:10: error: 'const struct drm_bridge_funcs' has no member named 'post_disable'
211 | .post_disable = dp_bridge_post_disable,
| ^~~~~~~~~~~~
drivers/gpu/drm/msm/dp/dp_drm.c:211:25: warning: excess elements in struct initializer
211 | .post_disable = dp_bridge_post_disable,
| ^~~~~~~~~~~~~~~~~~~~~~
drivers/gpu/drm/msm/dp/dp_drm.c:211:25: note: (near initialization for 'dp_bridge_ops')
drivers/gpu/drm/msm/dp/dp_drm.c:212:10: error: 'const struct drm_bridge_funcs' has no member named 'mode_set'
212 | .mode_set = dp_bridge_mode_set,
| ^~~~~~~~
drivers/gpu/drm/msm/dp/dp_drm.c:212:25: warning: excess elements in struct initializer
212 | .mode_set = dp_bridge_mode_set,
| ^~~~~~~~~~~~~~~~~~
drivers/gpu/drm/msm/dp/dp_drm.c:212:25: note: (near initialization for 'dp_bridge_ops')
drivers/gpu/drm/msm/dp/dp_drm.c: In function 'msm_dp_bridge_init':
drivers/gpu/drm/msm/dp/dp_drm.c:229:15: error: invalid use of undefined type 'struct drm_bridge'
229 | bridge->funcs = &dp_bridge_ops;
| ^~
drivers/gpu/drm/msm/dp/dp_drm.c:230:15: error: invalid use of undefined type 'struct drm_bridge'
230 | bridge->encoder = encoder;
| ^~
drivers/gpu/drm/msm/dp/dp_drm.c:232:14: error: implicit declaration of function 'drm_bridge_attach'; did you mean 'drm_bridge_detach'? [-Werror=implicit-function-declaration]
232 | rc = drm_bridge_attach(encoder, bridge, NULL, DRM_BRIDGE_ATTACH_NO_CONNECTOR);
| ^~~~~~~~~~~~~~~~~
| drm_bridge_detach
drivers/gpu/drm/msm/dp/dp_drm.c:232:55: error: 'DRM_BRIDGE_ATTACH_NO_CONNECTOR' undeclared (first use in this function)
232 | rc = drm_bridge_attach(encoder, bridge, NULL, DRM_BRIDGE_ATTACH_NO_CONNECTOR);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/gpu/drm/msm/dp/dp_drm.c:232:55: note: each undeclared identifier is reported only once for each function it appears in
drivers/gpu/drm/msm/dp/dp_drm.c: At top level:
drivers/gpu/drm/msm/dp/dp_drm.c:208:38: error: storage size of 'dp_bridge_ops' isn't known
208 | static const struct drm_bridge_funcs dp_bridge_ops = {
| ^~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +209 drivers/gpu/drm/msm/dp/dp_drm.c
207
208 static const struct drm_bridge_funcs dp_bridge_ops = {
> 209 .enable = dp_bridge_enable,
210 .disable = dp_bridge_disable,
211 .post_disable = dp_bridge_post_disable,
212 .mode_set = dp_bridge_mode_set,
213 };
214
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-07-09 0:14 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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