From: kernel test robot <lkp@intel.com>
To: Guangshuo Li <lgs201920130244@gmail.com>,
Bin Liu <bin.liu@mediatek.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Nicolas Dufresne <nicolas.dufresne@collabora.com>,
Fan Wu <fanwu01@zju.edu.cn>, Hans Verkuil <hverkuil@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-media@vger.kernel.org,
Guangshuo Li <lgs201920130244@gmail.com>
Subject: Re: [PATCH] media: mtk-jpeg: drain hardware completion before freeing context
Date: Mon, 3 Aug 2026 20:55:13 +0800 [thread overview]
Message-ID: <202608032056.zBdPisX5-lkp@intel.com> (raw)
In-Reply-To: <20260708120833.755998-1-lgs201920130244@gmail.com>
Hi Guangshuo,
kernel test robot noticed the following build errors:
[auto build test ERROR on linuxtv-media-pending/master]
[also build test ERROR on media-tree/master linus/master v7.2-rc6 next-20260731]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Guangshuo-Li/media-mtk-jpeg-drain-hardware-completion-before-freeing-context/20260803-143440
base: https://git.linuxtv.org/media-ci/media-pending.git master
patch link: https://lore.kernel.org/r/20260708120833.755998-1-lgs201920130244%40gmail.com
patch subject: [PATCH] media: mtk-jpeg: drain hardware completion before freeing context
config: arm-randconfig-004-20260803 (https://download.01.org/0day-ci/archive/20260803/202608032056.zBdPisX5-lkp@intel.com/config)
compiler: clang version 21.1.8 (https://github.com/llvm/llvm-project 2078da43e25a4623cab2d0d60decddf709aaea28)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260803/202608032056.zBdPisX5-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/202608032056.zBdPisX5-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/media/platform/mediatek/jpeg/mtk_jpeg_core.c:1207:3: error: call to undeclared function 'mtk_jpeg_release_hw'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
1207 | mtk_jpeg_release_hw(jpeg, ctx);
| ^
drivers/media/platform/mediatek/jpeg/mtk_jpeg_core.c:1207:3: note: did you mean 'mtk_jpeg_release'?
drivers/media/platform/mediatek/jpeg/mtk_jpeg_core.c:1200:12: note: 'mtk_jpeg_release' declared here
1200 | static int mtk_jpeg_release(struct file *file)
| ^
1201 | {
1202 | struct mtk_jpeg_dev *jpeg = video_drvdata(file);
1203 | struct mtk_jpeg_ctx *ctx = mtk_jpeg_file_to_ctx(file);
1204 |
1205 | if (jpeg->variant->jpeg_worker) {
1206 | cancel_work_sync(&ctx->jpeg_work);
1207 | mtk_jpeg_release_hw(jpeg, ctx);
| ~~~~~~~~~~~~~~~~~~~
| mtk_jpeg_release
1 error generated.
vim +/mtk_jpeg_release_hw +1207 drivers/media/platform/mediatek/jpeg/mtk_jpeg_core.c
1199
1200 static int mtk_jpeg_release(struct file *file)
1201 {
1202 struct mtk_jpeg_dev *jpeg = video_drvdata(file);
1203 struct mtk_jpeg_ctx *ctx = mtk_jpeg_file_to_ctx(file);
1204
1205 if (jpeg->variant->jpeg_worker) {
1206 cancel_work_sync(&ctx->jpeg_work);
> 1207 mtk_jpeg_release_hw(jpeg, ctx);
1208 }
1209
1210 mutex_lock(&jpeg->lock);
1211 v4l2_m2m_ctx_release(ctx->fh.m2m_ctx);
1212 v4l2_ctrl_handler_free(&ctx->ctrl_hdl);
1213 v4l2_fh_del(&ctx->fh, file);
1214 v4l2_fh_exit(&ctx->fh);
1215 kfree(ctx);
1216 mutex_unlock(&jpeg->lock);
1217 return 0;
1218 }
1219
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2026-08-03 12:55 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260708120833.755998-1-lgs201920130244@gmail.com>]
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=202608032056.zBdPisX5-lkp@intel.com \
--to=lkp@intel.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bin.liu@mediatek.com \
--cc=fanwu01@zju.edu.cn \
--cc=hverkuil@kernel.org \
--cc=lgs201920130244@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=nicolas.dufresne@collabora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox