From: kernel test robot <lkp@intel.com>
To: Dmitry Baryshkov <lumag@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Jessica Zhang <quic_jesszhan@quicinc.com>
Subject: drivers/gpu/drm/msm/hdmi/hdmi.c:439:1: sparse: sparse: symbol 'msm_hdmi_pm_ops' was not declared. Should it be static?
Date: Mon, 19 Jan 2026 19:11:03 +0800 [thread overview]
Message-ID: <202601191930.05BnzKNA-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 24d479d26b25bce5faea3ddd9fa8f3a6c3129ea7
commit: 0c5ec818cc166b4633c5f12e26abfddb57f6af9f drm/msm/hdmi: implement proper runtime PM handling
date: 8 months ago
config: powerpc-randconfig-r131-20260118 (https://download.01.org/0day-ci/archive/20260119/202601191930.05BnzKNA-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 9.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260119/202601191930.05BnzKNA-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/202601191930.05BnzKNA-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/msm/hdmi/hdmi.c:439:1: sparse: sparse: symbol 'msm_hdmi_pm_ops' was not declared. Should it be static?
vim +/msm_hdmi_pm_ops +439 drivers/gpu/drm/msm/hdmi/hdmi.c
438
> 439 DEFINE_RUNTIME_DEV_PM_OPS(msm_hdmi_pm_ops, msm_hdmi_runtime_suspend, msm_hdmi_runtime_resume, NULL);
440
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-01-19 11:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 11:11 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-13 18:31 kernel test robot
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=202601191930.05BnzKNA-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=quic_jesszhan@quicinc.com \
/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®