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: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [avpatel:riscv_aia_v1 16/18] drivers/irqchip/irq-riscv-imsic.c:267:12: error: 'struct imsic_priv' has no member named 'base_ipi'
Date: Fri, 2 Jul 2021 21:16:50 +0800	[thread overview]
Message-ID: <202107022144.2gbfHp4W-lkp@intel.com> (raw)

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

tree:   https://github.com/avpatel/linux.git riscv_aia_v1
head:   13d6f29527fb19a1c2ed6e52479b031c219c5bca
commit: d9e4c59d8e5c057d5e60ca6f854084667fd3106e [16/18] irqchip: Add RISC-V incoming MSI controller driver
config: riscv-randconfig-s031-20210702 (attached as .config)
compiler: riscv64-linux-gcc (GCC) 9.3.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # apt-get install sparse
        # sparse version: v0.6.3-341-g8af24329-dirty
        # https://github.com/avpatel/linux/commit/d9e4c59d8e5c057d5e60ca6f854084667fd3106e
        git remote add avpatel https://github.com/avpatel/linux.git
        git fetch --no-tags avpatel riscv_aia_v1
        git checkout d9e4c59d8e5c057d5e60ca6f854084667fd3106e
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=riscv SHELL=/bin/bash drivers/

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: In function 'imsic_ids_local_sync':
>> drivers/irqchip/irq-riscv-imsic.c:267:12: error: 'struct imsic_priv' has no member named 'base_ipi'
     267 |   if ((priv->base_ipi <= i) &&
         |            ^~
   drivers/irqchip/irq-riscv-imsic.c:268:17: error: 'struct imsic_priv' has no member named 'base_ipi'
     268 |       (i < (priv->base_ipi + priv->nr_ipis)))
         |                 ^~
>> drivers/irqchip/irq-riscv-imsic.c:268:36: error: 'struct imsic_priv' has no member named 'nr_ipis'; did you mean 'nr_ids'?
     268 |       (i < (priv->base_ipi + priv->nr_ipis)))
         |                                    ^~~~~~~
         |                                    nr_ids


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

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

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

                 reply	other threads:[~2021-07-02 13:17 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=202107022144.2gbfHp4W-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=anup.patel@wdc.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