From: kernel test robot <lkp@intel.com>
To: Robert Foss <robert.foss@linaro.org>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org,
Andrey Konovalov <andrey.konovalov@linaro.org>,
Hans Verkuil <hverkuil@xs4all.nl>
Subject: drivers/media/platform/qcom/camss/camss-vfe-170.c:191:20: warning: unused function 'vfe_reg_clr'
Date: Sun, 5 Sep 2021 17:06:41 +0800 [thread overview]
Message-ID: <202109051732.PmdsMUD9-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2940 bytes --]
Hi Robert,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 49624efa65ac9889f4e7c7b2452b2e6ce42ba37d
commit: 7319cdf189bb643c6d56e5898ef89ad7c3ef6c31 media: camss: Add support for VFE hardware version Titan 170
date: 6 months ago
config: mips-randconfig-r003-20210904 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 1104e3258b5064e7110cc297e2cec60ac9acfc0a)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install mips cross compiling tool for clang build
# apt-get install binutils-mips-linux-gnu
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7319cdf189bb643c6d56e5898ef89ad7c3ef6c31
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout 7319cdf189bb643c6d56e5898ef89ad7c3ef6c31
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross O=build_dir ARCH=mips SHELL=/bin/bash drivers/media/platform/qcom/camss/ kernel/time/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/media/platform/qcom/camss/camss-vfe-170.c:191:20: warning: unused function 'vfe_reg_clr'
static inline void vfe_reg_clr(struct vfe_device u32 reg, u32 clr_bits)
^
fatal error: error in backend: Nested variants found in inline asm string: '.if ( 0x00 ) != -1)) 0x00 ) != -1)) : ($( static struct ftrace_branch_data __attribute__((__aligned__(4))) __attribute__((__section__("_ftrace_branch"))) __if_trace = $( .func = __func__, .file = "arch/mips/include/asm/barrier.h", .line = 16, $); 0x00 ) != -1)) : $))) ) && ( (1 << 0) ); .set push; .set mips64r2; .rept 1; sync 0x00; .endr; .set pop; .else; ; .endif'
clang-14: error: clang frontend command failed with exit code 70 (use -v to see invocation)
clang version 14.0.0 (git://gitmirror/llvm_project 6fe2beba7d2a41964af658c8c59dd172683ef739)
Target: mips-unknown-linux
Thread model: posix
InstalledDir: /opt/cross/clang-6fe2beba7d/bin
clang-14: note: diagnostic msg:
Makefile arch drivers include kernel net scripts security sound source usr
vim +/vfe_reg_clr +191 drivers/media/platform/qcom/camss/camss-vfe-170.c
190
> 191 static inline void vfe_reg_clr(struct vfe_device *vfe, u32 reg, u32 clr_bits)
192 {
193 u32 bits = readl_relaxed(vfe->base + reg);
194
195 writel_relaxed(bits & ~clr_bits, vfe->base + reg);
196 }
197
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 37531 bytes --]
next reply other threads:[~2021-09-05 9:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-05 9:06 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-08-21 7:35 drivers/media/platform/qcom/camss/camss-vfe-170.c:191:20: warning: unused function 'vfe_reg_clr' 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=202109051732.PmdsMUD9-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrey.konovalov@linaro.org \
--cc=hverkuil@xs4all.nl \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=robert.foss@linaro.org \
/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