From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [chrome-os:chromeos-6.6 138/138] drivers/soc/mediatek/mtk-dpc.c:470:24: sparse: sparse: symbol 'mtk_dpc_driver' was not declared. Should it be static?
Date: Fri, 30 May 2025 14:13:37 +0800 [thread overview]
Message-ID: <202505301435.vTHMKFDA-lkp@intel.com> (raw)
tree: https://chromium.googlesource.com/chromiumos/third_party/kernel chromeos-6.6
head: c76c68baa3b1801d81033deae4c36dd8dfe350f5
commit: 073720863458cfc81c898a81e68932cd296b3e37 [138/138] CHROMIUM: drm/mediatek: add display MMDVFS and MMQoS Support
config: arm-randconfig-r121-20250529 (https://download.01.org/0day-ci/archive/20250530/202505301435.vTHMKFDA-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 14.3.0
reproduce: (https://download.01.org/0day-ci/archive/20250530/202505301435.vTHMKFDA-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202505301435.vTHMKFDA-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/soc/mediatek/mtk-dpc.c:470:24: sparse: sparse: symbol 'mtk_dpc_driver' was not declared. Should it be static?
--
>> drivers/gpu/drm/mediatek/mtk_drm_drv.c:877:73: sparse: sparse: Using plain integer as NULL pointer
drivers/gpu/drm/mediatek/mtk_drm_drv.c:359:10: sparse: sparse: Initializer entry defined twice
drivers/gpu/drm/mediatek/mtk_drm_drv.c:363:10: sparse: also defined here
vim +/mtk_dpc_driver +470 drivers/soc/mediatek/mtk-dpc.c
469
> 470 struct platform_driver mtk_dpc_driver = {
471 .probe = mtk_dpc_probe,
472 .remove = mtk_dpc_remove,
473 .driver = {
474 .name = "mediatek-disp-dpc",
475 .owner = THIS_MODULE,
476 .of_match_table = mtk_dpc_driver_dt_match,
477 },
478 };
479 module_platform_driver(mtk_dpc_driver);
480
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-05-30 6:13 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=202505301435.vTHMKFDA-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.