From: kernel test robot <lkp@intel.com>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [lst:imx8mq-vpu-blk-ctrl 22/23] drivers/staging/media/hantro/hantro_drv.c:594:12: error: field name not in record or union initializer
Date: Fri, 12 Nov 2021 18:55:18 +0800 [thread overview]
Message-ID: <202111121810.9v11LOZ2-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 7415 bytes --]
tree: https://git.pengutronix.de/git/lst/linux imx8mq-vpu-blk-ctrl
head: 2cd41211c1291460262d24269ae37db016dadf82
commit: 89853879eff9bbcf33b45b7f0000c95042cd45c2 [22/23] HACK: media: hantro: split i.MX8MQ G1 code
config: m68k-allmodconfig (attached as .config)
compiler: m68k-linux-gcc (GCC) 11.2.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 lst https://git.pengutronix.de/git/lst/linux
git fetch --no-tags lst imx8mq-vpu-blk-ctrl
git checkout 89853879eff9bbcf33b45b7f0000c95042cd45c2
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=m68k SHELL=/bin/bash drivers/staging/media/hantro/
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/staging/media/hantro/hantro_drv.c:594:12: error: field name not in record or union initializer
594 | {{ .compatible = "nxp,imx8mq-vpu-g1", .data = &imx8mq_g1_vpu_variant, },
| ^
drivers/staging/media/hantro/hantro_drv.c:594:12: note: (near initialization for 'of_hantro_match[7].name')
drivers/staging/media/hantro/hantro_drv.c:594:47: error: field name not in record or union initializer
594 | {{ .compatible = "nxp,imx8mq-vpu-g1", .data = &imx8mq_g1_vpu_variant, },
| ^
drivers/staging/media/hantro/hantro_drv.c:594:47: note: (near initialization for 'of_hantro_match[7].name')
>> drivers/staging/media/hantro/hantro_drv.c:594:55: error: excess elements in struct initializer
594 | {{ .compatible = "nxp,imx8mq-vpu-g1", .data = &imx8mq_g1_vpu_variant, },
| ^
drivers/staging/media/hantro/hantro_drv.c:594:55: note: (near initialization for 'of_hantro_match[7].name')
drivers/staging/media/hantro/hantro_drv.c:595:11: error: field name not in record or union initializer
595 | { .compatible = "nxp,imx8mq-vpu-g2", .data = &imx8mq_vpu_g2_variant },
| ^
drivers/staging/media/hantro/hantro_drv.c:595:11: note: (near initialization for 'of_hantro_match[7].type')
drivers/staging/media/hantro/hantro_drv.c:595:46: error: field name not in record or union initializer
595 | { .compatible = "nxp,imx8mq-vpu-g2", .data = &imx8mq_vpu_g2_variant },
| ^
drivers/staging/media/hantro/hantro_drv.c:595:46: note: (near initialization for 'of_hantro_match[7].type')
drivers/staging/media/hantro/hantro_drv.c:595:54: error: excess elements in struct initializer
595 | { .compatible = "nxp,imx8mq-vpu-g2", .data = &imx8mq_vpu_g2_variant },
| ^
drivers/staging/media/hantro/hantro_drv.c:595:54: note: (near initialization for 'of_hantro_match[7].type')
drivers/staging/media/hantro/hantro_drv.c:598:11: error: field name not in record or union initializer
598 | { .compatible = "microchip,sama5d4-vdec", .data = &sama5d4_vdec_variant, },
| ^
drivers/staging/media/hantro/hantro_drv.c:598:11: note: (near initialization for 'of_hantro_match[7].compatible')
drivers/staging/media/hantro/hantro_drv.c:598:51: error: field name not in record or union initializer
598 | { .compatible = "microchip,sama5d4-vdec", .data = &sama5d4_vdec_variant, },
| ^
drivers/staging/media/hantro/hantro_drv.c:598:51: note: (near initialization for 'of_hantro_match[7].compatible')
drivers/staging/media/hantro/hantro_drv.c:598:59: error: excess elements in struct initializer
598 | { .compatible = "microchip,sama5d4-vdec", .data = &sama5d4_vdec_variant, },
| ^
drivers/staging/media/hantro/hantro_drv.c:598:59: note: (near initialization for 'of_hantro_match[7].compatible')
drivers/staging/media/hantro/hantro_drv.c:600:9: error: braces around scalar initializer [-Werror]
600 | { /* sentinel */ }
| ^
drivers/staging/media/hantro/hantro_drv.c:600:9: note: (near initialization for 'of_hantro_match[7].data')
>> drivers/staging/media/hantro/hantro_drv.c:600:9: error: empty scalar initializer
drivers/staging/media/hantro/hantro_drv.c:600:9: note: (near initialization for 'of_hantro_match[7].data')
>> drivers/staging/media/hantro/hantro_drv.c:601:2: error: expected '}' before ';' token
601 | };
| ^
drivers/staging/media/hantro/hantro_drv.c:583:54: note: to match this '{'
583 | static const struct of_device_id of_hantro_match[] = {
| ^
>> drivers/staging/media/hantro/hantro_drv.c:583:34: error: 'of_hantro_match' defined but not used [-Werror=unused-const-variable=]
583 | static const struct of_device_id of_hantro_match[] = {
| ^~~~~~~~~~~~~~~
>> drivers/staging/media/hantro/hantro_drv.c:574:42: error: 'hantro_fops' defined but not used [-Werror=unused-const-variable=]
574 | static const struct v4l2_file_operations hantro_fops = {
| ^~~~~~~~~~~
>> drivers/staging/media/hantro/hantro_drv.c:182:28: error: 'vpu_m2m_ops' defined but not used [-Werror=unused-variable]
182 | static struct v4l2_m2m_ops vpu_m2m_ops = {
| ^~~~~~~~~~~
cc1: all warnings being treated as errors
vim +594 drivers/staging/media/hantro/hantro_drv.c
573
> 574 static const struct v4l2_file_operations hantro_fops = {
575 .owner = THIS_MODULE,
576 .open = hantro_open,
577 .release = hantro_release,
578 .poll = v4l2_m2m_fop_poll,
579 .unlocked_ioctl = video_ioctl2,
580 .mmap = v4l2_m2m_fop_mmap,
581 };
582
> 583 static const struct of_device_id of_hantro_match[] = {
584 #ifdef CONFIG_VIDEO_HANTRO_ROCKCHIP
585 { .compatible = "rockchip,px30-vpu", .data = &px30_vpu_variant, },
586 { .compatible = "rockchip,rk3036-vpu", .data = &rk3036_vpu_variant, },
587 { .compatible = "rockchip,rk3066-vpu", .data = &rk3066_vpu_variant, },
588 { .compatible = "rockchip,rk3288-vpu", .data = &rk3288_vpu_variant, },
589 { .compatible = "rockchip,rk3328-vpu", .data = &rk3328_vpu_variant, },
590 { .compatible = "rockchip,rk3399-vpu", .data = &rk3399_vpu_variant, },
591 #endif
592 #ifdef CONFIG_VIDEO_HANTRO_IMX8M
593 { .compatible = "nxp,imx8mq-vpu", .data = &imx8mq_vpu_variant, },
> 594 {{ .compatible = "nxp,imx8mq-vpu-g1", .data = &imx8mq_g1_vpu_variant, },
595 { .compatible = "nxp,imx8mq-vpu-g2", .data = &imx8mq_vpu_g2_variant },
596 #endif
597 #ifdef CONFIG_VIDEO_HANTRO_SAMA5D4
598 { .compatible = "microchip,sama5d4-vdec", .data = &sama5d4_vdec_variant, },
599 #endif
> 600 { /* sentinel */ }
> 601 };
602 MODULE_DEVICE_TABLE(of, of_hantro_match);
603
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 61357 bytes --]
reply other threads:[~2021-11-12 10:55 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=202111121810.9v11LOZ2-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=l.stach@pengutronix.de \
--cc=linux-kernel@vger.kernel.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