From: kernel test robot <lkp@intel.com>
To: Izhar Ameer Shaikh <izhar.ameer.shaikh@xilinx.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
Michal Simek <monstr@monstr.eu>,
Tanmay Shah <tanmay.shah@xilinx.com>,
Rajan Vaja <rajan.vaja@xilinx.com>,
Radhey Shyam Pandey <radhey.shyam.pandey@xilinx.com>
Subject: [xilinx-xlnx:master 40/773] include/linux/firmware/xlnx-zynqmp.h:1124:12: warning: unused function 'zynqmp_pm_sec_read_reg'
Date: Fri, 20 Jan 2023 23:11:13 +0800 [thread overview]
Message-ID: <202301202325.4Cm9ujVl-lkp@intel.com> (raw)
tree: https://github.com/Xilinx/linux-xlnx master
head: 155ae9648df275d38841cfe45231ba0471baa1cb
commit: 41adf9b5d9695095fe08233b2d702251b4081609 [40/773] firmware: xilinx: Add support for secure read/write ioctl interface
config: x86_64-randconfig-a012 (https://download.01.org/0day-ci/archive/20230120/202301202325.4Cm9ujVl-lkp@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project f28c006a5895fc0e329fe15fead81e37457cb1d1)
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
# https://github.com/Xilinx/linux-xlnx/commit/41adf9b5d9695095fe08233b2d702251b4081609
git remote add xilinx-xlnx https://github.com/Xilinx/linux-xlnx
git fetch --no-tags xilinx-xlnx master
git checkout 41adf9b5d9695095fe08233b2d702251b4081609
# 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=x86_64 olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
In file included from drivers/spi/spi-zynqmp-gqspi.c:13:
>> include/linux/firmware/xlnx-zynqmp.h:1124:12: warning: unused function 'zynqmp_pm_sec_read_reg' [-Wunused-function]
static int zynqmp_pm_sec_read_reg(u32 node_id, u32 offset, u32 *ret_value)
^
>> include/linux/firmware/xlnx-zynqmp.h:1129:12: warning: unused function 'zynqmp_pm_sec_mask_write_reg' [-Wunused-function]
static int zynqmp_pm_sec_mask_write_reg(const u32 node_id, const u32 offset,
^
2 warnings generated.
vim +/zynqmp_pm_sec_read_reg +1124 include/linux/firmware/xlnx-zynqmp.h
1123
> 1124 static int zynqmp_pm_sec_read_reg(u32 node_id, u32 offset, u32 *ret_value)
1125 {
1126 return -ENODEV;
1127 }
1128
> 1129 static int zynqmp_pm_sec_mask_write_reg(const u32 node_id, const u32 offset,
1130 u32 mask, u32 value)
1131 {
1132 return -ENODEV;
1133 }
1134
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2023-01-20 15:13 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=202301202325.4Cm9ujVl-lkp@intel.com \
--to=lkp@intel.com \
--cc=izhar.ameer.shaikh@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=monstr@monstr.eu \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=radhey.shyam.pandey@xilinx.com \
--cc=rajan.vaja@xilinx.com \
--cc=tanmay.shah@xilinx.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;
as well as URLs for NNTP newsgroup(s).