From: kernel test robot <lkp@intel.com>
To: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Jassi Brar <jassisinghbrar@gmail.com>,
Chia-I Wu <olvaffe@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Subject: drivers/mailbox/mtk-gpueb-mailbox.c:203:28: sparse: sparse: symbol 'mtk_gpueb_mbox_ops' was not declared. Should it be static?
Date: Fri, 10 Oct 2025 06:38:42 +0800 [thread overview]
Message-ID: <202510100629.3nGvrhEU-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 5472d60c129f75282d94ae5ad072ee6dfb7c7246
commit: dbca0eabb821a6278925712a7bb263d0997e9c8f mailbox: add MediaTek GPUEB IPI mailbox
date: 3 days ago
config: arc-randconfig-r112-20251010 (https://download.01.org/0day-ci/archive/20251010/202510100629.3nGvrhEU-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 12.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251010/202510100629.3nGvrhEU-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/202510100629.3nGvrhEU-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/mailbox/mtk-gpueb-mailbox.c:203:28: sparse: sparse: symbol 'mtk_gpueb_mbox_ops' was not declared. Should it be static?
vim +/mtk_gpueb_mbox_ops +203 drivers/mailbox/mtk-gpueb-mailbox.c
202
> 203 const struct mbox_chan_ops mtk_gpueb_mbox_ops = {
204 .send_data = mtk_gpueb_mbox_send_data,
205 .startup = mtk_gpueb_mbox_startup,
206 .shutdown = mtk_gpueb_mbox_shutdown,
207 .last_tx_done = mtk_gpueb_mbox_last_tx_done,
208 };
209
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-10-09 22:39 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=202510100629.3nGvrhEU-lkp@intel.com \
--to=lkp@intel.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=jassisinghbrar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.frattaroli@collabora.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=olvaffe@gmail.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