public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Boqun Feng <boqun.feng@gmail.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [boqun:dev/arm64 1/3] drivers/pci/controller/pci-hyperv.c:769:13: error: 'hv_set_msi_entry_from_desc' defined but not used
Date: Mon, 14 Feb 2022 06:02:04 +0800	[thread overview]
Message-ID: <202202140532.7tKzn8ca-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/boqun/linux.git dev/arm64
head:   715cdf131dd8fcb33591dc7143d193050368ecc1
commit: 39649970d5e2d161268189e1dcb9b3cb7a6ee03b [1/3] PCI: hv: Avoid the retarget interrupt hypercall in irq_unmask() on ARM64
config: arm64-allyesconfig (https://download.01.org/0day-ci/archive/20220214/202202140532.7tKzn8ca-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 11.2.0
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://git.kernel.org/pub/scm/linux/kernel/git/boqun/linux.git/commit/?id=39649970d5e2d161268189e1dcb9b3cb7a6ee03b
        git remote add boqun https://git.kernel.org/pub/scm/linux/kernel/git/boqun/linux.git
        git fetch --no-tags boqun dev/arm64
        git checkout 39649970d5e2d161268189e1dcb9b3cb7a6ee03b
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arm64 SHELL=/bin/bash arch/arm64/ drivers/pci/ kernel//

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

>> drivers/pci/controller/pci-hyperv.c:769:13: error: 'hv_set_msi_entry_from_desc' defined but not used [-Werror=unused-function]
     769 | static void hv_set_msi_entry_from_desc(union hv_msi_entry *msi_entry,
         |             ^~~~~~~~~~~~~~~~~~~~~~~~~~
   cc1: all warnings being treated as errors


vim +/hv_set_msi_entry_from_desc +769 drivers/pci/controller/pci-hyperv.c

d9932b46915664 Sunil Muthuswamy 2022-01-05  768  
d9932b46915664 Sunil Muthuswamy 2022-01-05 @769  static void hv_set_msi_entry_from_desc(union hv_msi_entry *msi_entry,
d9932b46915664 Sunil Muthuswamy 2022-01-05  770  				       struct msi_desc *msi_desc)
d9932b46915664 Sunil Muthuswamy 2022-01-05  771  {
d9932b46915664 Sunil Muthuswamy 2022-01-05  772  	msi_entry->address = ((u64)msi_desc->msg.address_hi << 32) |
d9932b46915664 Sunil Muthuswamy 2022-01-05  773  			      msi_desc->msg.address_lo;
d9932b46915664 Sunil Muthuswamy 2022-01-05  774  	msi_entry->data = msi_desc->msg.data;
d9932b46915664 Sunil Muthuswamy 2022-01-05  775  }
d9932b46915664 Sunil Muthuswamy 2022-01-05  776  

:::::: The code at line 769 was first introduced by commit
:::::: d9932b46915664c88709d59927fa67e797adec56 PCI: hv: Add arm64 Hyper-V vPCI support

:::::: TO: Sunil Muthuswamy <sunilmut@microsoft.com>
:::::: CC: Bjorn Helgaas <bhelgaas@google.com>

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

                 reply	other threads:[~2022-02-13 22:02 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=202202140532.7tKzn8ca-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=boqun.feng@gmail.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.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