From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com,
Guenter Roeck <groeck@google.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [chrome-os:chromeos-5.10 130/150] drivers/media/platform/mtk-jpeg/mtk_jpeg_core.c:1857:38: warning: unused variable 'mtk8195_jpegdec_drvdata'
Date: Sat, 27 May 2023 12:24:36 +0800 [thread overview]
Message-ID: <202305271206.yyLblmbY-lkp@intel.com> (raw)
tree: https://chromium.googlesource.com/chromiumos/third_party/kernel chromeos-5.10
head: 9de748741e802680a1c2540e75fb3f3dba98d8be
commit: 44de16ae73f5ca7500460d916a7d6e1b44d2b090 [130/150] BACKPORT: UPSTREAM: media: mtk-jpegdec: add jpeg decode worker interface
config: hexagon-randconfig-r022-20230526 (https://download.01.org/0day-ci/archive/20230527/202305271206.yyLblmbY-lkp@intel.com/config)
compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project 4faf3aaf28226a4e950c103a14f6fc1d1fdabb1b)
reproduce (this is a W=1 build):
mkdir -p ~/bin
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git remote add chrome-os https://chromium.googlesource.com/chromiumos/third_party/kernel
git fetch --no-tags chrome-os chromeos-5.10
git checkout 44de16ae73f5ca7500460d916a7d6e1b44d2b090
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang ~/bin/make.cross W=1 O=build_dir ARCH=hexagon olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang ~/bin/make.cross W=1 O=build_dir ARCH=hexagon SHELL=/bin/bash M=drivers/media/platform/mtk-jpeg
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202305271206.yyLblmbY-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/media/platform/mtk-jpeg/mtk_jpeg_core.c:1816:38: warning: unused variable 'mt8173_jpeg_drvdata' [-Wunused-const-variable]
static const struct mtk_jpeg_variant mt8173_jpeg_drvdata = {
^
drivers/media/platform/mtk-jpeg/mtk_jpeg_core.c:1831:38: warning: unused variable 'mtk_jpeg_drvdata' [-Wunused-const-variable]
static const struct mtk_jpeg_variant mtk_jpeg_drvdata = {
^
drivers/media/platform/mtk-jpeg/mtk_jpeg_core.c:1846:32: warning: unused variable 'mtk8195_jpegenc_drvdata' [-Wunused-variable]
static struct mtk_jpeg_variant mtk8195_jpegenc_drvdata = {
^
>> drivers/media/platform/mtk-jpeg/mtk_jpeg_core.c:1857:38: warning: unused variable 'mtk8195_jpegdec_drvdata' [-Wunused-const-variable]
static const struct mtk_jpeg_variant mtk8195_jpegdec_drvdata = {
^
4 warnings generated.
vim +/mtk8195_jpegdec_drvdata +1857 drivers/media/platform/mtk-jpeg/mtk_jpeg_core.c
1856
> 1857 static const struct mtk_jpeg_variant mtk8195_jpegdec_drvdata = {
1858 .formats = mtk_jpeg_dec_formats,
1859 .num_formats = MTK_JPEG_DEC_NUM_FORMATS,
1860 .qops = &mtk_jpeg_dec_qops,
1861 .m2m_ops = &mtk_jpeg_multicore_dec_m2m_ops,
1862 .dev_name = "mtk-jpeg-dec",
1863 .ioctl_ops = &mtk_jpeg_dec_ioctl_ops,
1864 .out_q_default_fourcc = V4L2_PIX_FMT_JPEG,
1865 .cap_q_default_fourcc = V4L2_PIX_FMT_YUV420M,
1866 };
1867
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-05-27 4:24 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=202305271206.yyLblmbY-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--cc=groeck@google.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;
as well as URLs for NNTP newsgroup(s).