public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Anup Patel <anup.patel@wdc.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	linux-kernel@vger.kernel.org
Subject: [avpatel:riscv_kvm_aia_v1 35/45] drivers/irqchip/irq-riscv-imsic.c:268:14: error: no member named 'base_ipi' in 'struct imsic_priv'
Date: Tue, 31 Aug 2021 03:28:37 +0800	[thread overview]
Message-ID: <202108310328.kFbksNrA-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3933 bytes --]

tree:   https://github.com/avpatel/linux.git riscv_kvm_aia_v1
head:   4d42d8db925fe52a94a12e9cd93c06f252d5dfbb
commit: a086e3962fd40d4296e9dc4ea490510d93786712 [35/45] irqchip: Add RISC-V incoming MSI controller driver
config: riscv-randconfig-r004-20210830 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 4b1fde8a2b681dad2ce0c082a5d6422caa06b0bc)
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 riscv cross compiling tool for clang build
        # apt-get install binutils-riscv64-linux-gnu
        # https://github.com/avpatel/linux/commit/a086e3962fd40d4296e9dc4ea490510d93786712
        git remote add avpatel https://github.com/avpatel/linux.git
        git fetch --no-tags avpatel riscv_kvm_aia_v1
        git checkout a086e3962fd40d4296e9dc4ea490510d93786712
        # save the attached .config to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross O=build_dir ARCH=riscv SHELL=/bin/bash drivers/irqchip/

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/irqchip/irq-riscv-imsic.c:268:14: error: no member named 'base_ipi' in 'struct imsic_priv'
                   if ((priv->base_ipi <= i) &&
                        ~~~~  ^
   drivers/irqchip/irq-riscv-imsic.c:269:19: error: no member named 'base_ipi' in 'struct imsic_priv'
                       (i < (priv->base_ipi + priv->nr_ipis)))
                             ~~~~  ^
>> drivers/irqchip/irq-riscv-imsic.c:269:36: error: no member named 'nr_ipis' in 'struct imsic_priv'; did you mean 'nr_ids'?
                       (i < (priv->base_ipi + priv->nr_ipis)))
                                                    ^~~~~~~
                                                    nr_ids
   drivers/irqchip/irq-riscv-imsic.c:69:6: note: 'nr_ids' declared here
           u32 nr_ids;
               ^
   drivers/irqchip/irq-riscv-imsic.c:906:19: error: no member named 'base_ipi' in 'struct imsic_priv'
                                          &priv->base_ipi))
                                           ~~~~  ^
   drivers/irqchip/irq-riscv-imsic.c:907:9: error: no member named 'base_ipi' in 'struct imsic_priv'
                   priv->base_ipi = 0;
                   ~~~~  ^
   drivers/irqchip/irq-riscv-imsic.c:909:19: error: no member named 'nr_ipis' in 'struct imsic_priv'; did you mean 'nr_ids'?
                                          &priv->nr_ipis))
                                                 ^~~~~~~
                                                 nr_ids
   drivers/irqchip/irq-riscv-imsic.c:69:6: note: 'nr_ids' declared here
           u32 nr_ids;
               ^
   drivers/irqchip/irq-riscv-imsic.c:910:9: error: no member named 'nr_ipis' in 'struct imsic_priv'; did you mean 'nr_ids'?
                   priv->nr_ipis = 0;
                         ^~~~~~~
                         nr_ids
   drivers/irqchip/irq-riscv-imsic.c:69:6: note: 'nr_ids' declared here
           u32 nr_ids;
               ^
   7 errors generated.


vim +268 drivers/irqchip/irq-riscv-imsic.c

   261	
   262	static void imsic_ids_local_sync(struct imsic_priv *priv)
   263	{
   264		int i;
   265	
   266		raw_spin_lock(&priv->ids_lock);
   267		for (i = 1; i <= priv->nr_ids; i++) {
 > 268			if ((priv->base_ipi <= i) &&
 > 269			    (i < (priv->base_ipi + priv->nr_ipis)))
   270				continue;
   271			if (test_bit(i, priv->ids_enabled_bimap))
   272				csr_write(CSR_SETEIENUM, i);
   273			else
   274				csr_write(CSR_CLREIENUM, i);
   275		}
   276		raw_spin_unlock(&priv->ids_lock);
   277	}
   278	

---
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: 31078 bytes --]

                 reply	other threads:[~2021-08-30 19:28 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=202108310328.kFbksNrA-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=anup.patel@wdc.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@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