From: kernel test robot <lkp@intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: drivers/gpu/drm/amd/amdgpu/amdgpu_rap.c:110:37: warning: unused variable 'amdgpu_rap_debugfs_ops'
Date: Mon, 20 Feb 2023 03:08:58 +0800 [thread overview]
Message-ID: <202302200339.Whql7Emr-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 925cf0457d7e62ce08878ffb789189ac08ca8677
commit: df99e7bbbec3180693b3d932a9cbc88346e2a30e ARM: omap1: use pci_remap_iospace() for omap_cf
date: 10 months ago
config: arm-randconfig-r033-20230220 (https://download.01.org/0day-ci/archive/20230220/202302200339.Whql7Emr-lkp@intel.com/config)
compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project db89896bbbd2251fff457699635acbbedeead27f)
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 arm cross compiling tool for clang build
# apt-get install binutils-arm-linux-gnueabi
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=df99e7bbbec3180693b3d932a9cbc88346e2a30e
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout df99e7bbbec3180693b3d932a9cbc88346e2a30e
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm SHELL=/bin/bash drivers/gpu/drm/amd/amdgpu/ drivers/gpu/drm/amd/pm/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202302200339.Whql7Emr-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/amd/amdgpu/amdgpu_rap.c:110:37: warning: unused variable 'amdgpu_rap_debugfs_ops' [-Wunused-const-variable]
static const struct file_operations amdgpu_rap_debugfs_ops = {
^
1 warning generated.
--
>> drivers/gpu/drm/amd/amdgpu/../pm/amdgpu_pm.c:38:34: warning: unused variable 'clocks' [-Wunused-const-variable]
static const struct cg_flag_name clocks[] = {
^
1 warning generated.
vim +/amdgpu_rap_debugfs_ops +110 drivers/gpu/drm/amd/amdgpu/amdgpu_rap.c
a4322e1881bed8 Wenhui Sheng 2020-08-11 109
a4322e1881bed8 Wenhui Sheng 2020-08-11 @110 static const struct file_operations amdgpu_rap_debugfs_ops = {
a4322e1881bed8 Wenhui Sheng 2020-08-11 111 .owner = THIS_MODULE,
a4322e1881bed8 Wenhui Sheng 2020-08-11 112 .read = NULL,
a4322e1881bed8 Wenhui Sheng 2020-08-11 113 .write = amdgpu_rap_debugfs_write,
a4322e1881bed8 Wenhui Sheng 2020-08-11 114 .llseek = default_llseek
a4322e1881bed8 Wenhui Sheng 2020-08-11 115 };
a4322e1881bed8 Wenhui Sheng 2020-08-11 116
:::::: The code at line 110 was first introduced by commit
:::::: a4322e1881bed80ddb904482f0b2e948fa7fd47e drm/amdgpu: add debugfs interface for RAP test
:::::: TO: Wenhui Sheng <Wenhui.Sheng@amd.com>
:::::: CC: Alex Deucher <alexander.deucher@amd.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-02-19 19:09 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=202302200339.Whql7Emr-lkp@intel.com \
--to=lkp@intel.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--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).