From: kernel test robot <lkp@intel.com>
To: Claudiu Beznea <claudiu.beznea@microchip.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Vinod Koul <vkoul@kernel.org>,
Tudor Ambarus <tudor.ambarus@microchip.com>
Subject: [linux-next:master 7805/10748] drivers/dma/at_xdmac.c:2210:32: warning: unused variable 'atmel_xdmac_dev_pm_ops'
Date: Mon, 25 Oct 2021 13:13:56 +0800 [thread overview]
Message-ID: <202110251344.LPTlkbN4-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2480 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: cf6c9d12750cf6f3f6aeffcd0bdb36b1ac993f44
commit: 8e0c7e486014f8e924f5dc8f7a8719adb48f9d92 [7805/10748] dmaengine: at_xdmac: use pm_ptr()
config: arm-randconfig-r016-20211025 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project a461fa64bb37cffd73f683c74f6b0780379fc2ca)
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/next/linux-next.git/commit/?id=8e0c7e486014f8e924f5dc8f7a8719adb48f9d92
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 8e0c7e486014f8e924f5dc8f7a8719adb48f9d92
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 ARCH=arm
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/dma/at_xdmac.c:2210:32: warning: unused variable 'atmel_xdmac_dev_pm_ops' [-Wunused-const-variable]
static const struct dev_pm_ops atmel_xdmac_dev_pm_ops = {
^
1 warning generated.
vim +/atmel_xdmac_dev_pm_ops +2210 drivers/dma/at_xdmac.c
e1f7c9eee70730 Ludovic Desroches 2014-10-22 2209
e1f7c9eee70730 Ludovic Desroches 2014-10-22 @2210 static const struct dev_pm_ops atmel_xdmac_dev_pm_ops = {
e1f7c9eee70730 Ludovic Desroches 2014-10-22 2211 .prepare = atmel_xdmac_prepare,
e1f7c9eee70730 Ludovic Desroches 2014-10-22 2212 SET_LATE_SYSTEM_SLEEP_PM_OPS(atmel_xdmac_suspend, atmel_xdmac_resume)
e1f7c9eee70730 Ludovic Desroches 2014-10-22 2213 };
e1f7c9eee70730 Ludovic Desroches 2014-10-22 2214
:::::: The code at line 2210 was first introduced by commit
:::::: e1f7c9eee70730d7e6ec77f7ecc76f936e262cf0 dmaengine: at_xdmac: creation of the atmel eXtended DMA Controller driver
:::::: TO: Ludovic Desroches <ludovic.desroches@atmel.com>
:::::: CC: Vinod Koul <vinod.koul@intel.com>
---
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: 30119 bytes --]
reply other threads:[~2021-10-25 5:14 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=202110251344.LPTlkbN4-lkp@intel.com \
--to=lkp@intel.com \
--cc=claudiu.beznea@microchip.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=tudor.ambarus@microchip.com \
--cc=vkoul@kernel.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;
as well as URLs for NNTP newsgroup(s).