From: kernel test robot <lkp@intel.com>
To: Anup Patel <apatel@ventanamicro.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [avpatel:riscv_imsic_imp_v2 15/18] drivers/irqchip/irq-riscv-imsic-state.c:219:30: error: no member named 'timer' in 'struct imsic_local_priv'
Date: Mon, 16 Dec 2024 07:39:23 +0800 [thread overview]
Message-ID: <202412160744.hqkoC7cI-lkp@intel.com> (raw)
tree: https://github.com/avpatel/linux.git riscv_imsic_imp_v2
head: f91932baa72fea7864a1c699072e15e13ef45064
commit: 67f6ccaa232fd93009a9f128691a4459ea86fa39 [15/18] irqchip/riscv-imsic: Separate next and previous pointers in IMSIC vector
config: riscv-randconfig-002-20241216 (https://download.01.org/0day-ci/archive/20241216/202412160744.hqkoC7cI-lkp@intel.com/config)
compiler: clang version 15.0.7 (https://github.com/llvm/llvm-project 8dfdcc7b7bf66834a761bd8de445840ef68e4d1a)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241216/202412160744.hqkoC7cI-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202412160744.hqkoC7cI-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/irqchip/irq-riscv-imsic-state.c:219:30: error: no member named 'timer' in 'struct imsic_local_priv'
if (!timer_pending(&lpriv->timer)) {
~~~~~ ^
drivers/irqchip/irq-riscv-imsic-state.c:220:11: error: no member named 'timer' in 'struct imsic_local_priv'
lpriv->timer.expires = jiffies + 1;
~~~~~ ^
drivers/irqchip/irq-riscv-imsic-state.c:221:25: error: no member named 'timer' in 'struct imsic_local_priv'
add_timer_on(&lpriv->timer, smp_processor_id());
~~~~~ ^
3 errors generated.
vim +219 drivers/irqchip/irq-riscv-imsic-state.c
208
209 void imsic_local_sync_all(bool force_all)
210 {
211 struct imsic_local_priv *lpriv = this_cpu_ptr(imsic->lpriv);
212 unsigned long flags;
213
214 raw_spin_lock_irqsave(&lpriv->lock, flags);
215
216 if (force_all)
217 bitmap_fill(lpriv->dirty_bitmap, imsic->global.nr_ids + 1);
218 if (!__imsic_local_sync(lpriv)) {
> 219 if (!timer_pending(&lpriv->timer)) {
220 lpriv->timer.expires = jiffies + 1;
221 add_timer_on(&lpriv->timer, smp_processor_id());
222 }
223 }
224
225 raw_spin_unlock_irqrestore(&lpriv->lock, flags);
226 }
227
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-12-15 23:39 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=202412160744.hqkoC7cI-lkp@intel.com \
--to=lkp@intel.com \
--cc=apatel@ventanamicro.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@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