From: kernel test robot <lkp@intel.com>
To: Hogan Wang <hogan.wang@huawei.com>,
x86@kernel.org, dave.hansen@linux.intel.com, kvm@vger.kernel.org,
alex.williamson@redhat.com
Cc: oe-kbuild-all@lists.linux.dev, weidong.huang@huawei.com,
yechuan@huawei.com, hogan.wang@huawei.com,
wangxinxin.wang@huawei.com, jianjay.zhou@huawei.com,
wangjie88@huawei.com
Subject: Re: [PATCH] x86/irq: introduce repair_irq try to repair CPU vector
Date: Thu, 24 Jul 2025 00:33:11 +0800 [thread overview]
Message-ID: <202507240030.11iG6frT-lkp@intel.com> (raw)
In-Reply-To: <20250723015045.1701-1-hogan.wang@huawei.com>
Hi Hogan,
kernel test robot noticed the following build errors:
[auto build test ERROR on tip/irq/core]
[also build test ERROR on tip/master tip/x86/core awilliam-vfio/next linus/master v6.16-rc7 next-20250723]
[cannot apply to tip/auto-latest awilliam-vfio/for-linus]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Hogan-Wang/x86-irq-introduce-repair_irq-try-to-repair-CPU-vector/20250723-095327
base: tip/irq/core
patch link: https://lore.kernel.org/r/20250723015045.1701-1-hogan.wang%40huawei.com
patch subject: [PATCH] x86/irq: introduce repair_irq try to repair CPU vector
config: openrisc-allnoconfig (https://download.01.org/0day-ci/archive/20250724/202507240030.11iG6frT-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250724/202507240030.11iG6frT-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/202507240030.11iG6frT-lkp@intel.com/
All errors (new ones prefixed by >>):
kernel/irq/manage.c: In function 'repair_irq':
>> kernel/irq/manage.c:1431:9: error: implicit declaration of function 'irq_domain_repair_irq'; did you mean 'irq_domain_free_irqs'? [-Wimplicit-function-declaration]
1431 | irq_domain_repair_irq(irq_desc_get_irq_data(desc));
| ^~~~~~~~~~~~~~~~~~~~~
| irq_domain_free_irqs
vim +1431 kernel/irq/manage.c
1420
1421
1422 void repair_irq(unsigned int irq)
1423 {
1424 struct irq_desc *desc = irq_to_desc(irq);
1425 unsigned long flags;
1426
1427 mutex_lock(&desc->request_mutex);
1428 chip_bus_lock(desc);
1429 raw_spin_lock_irqsave(&desc->lock, flags);
1430
> 1431 irq_domain_repair_irq(irq_desc_get_irq_data(desc));
1432
1433 raw_spin_unlock_irqrestore(&desc->lock, flags);
1434 chip_bus_sync_unlock(desc);
1435 mutex_unlock(&desc->request_mutex);
1436 }
1437 EXPORT_SYMBOL(repair_irq);
1438
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-07-23 16:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 1:50 [PATCH] x86/irq: introduce repair_irq try to repair CPU vector Hogan Wang
2025-07-23 15:08 ` Thomas Gleixner
2025-07-23 16:33 ` kernel test robot [this message]
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=202507240030.11iG6frT-lkp@intel.com \
--to=lkp@intel.com \
--cc=alex.williamson@redhat.com \
--cc=dave.hansen@linux.intel.com \
--cc=hogan.wang@huawei.com \
--cc=jianjay.zhou@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=wangjie88@huawei.com \
--cc=wangxinxin.wang@huawei.com \
--cc=weidong.huang@huawei.com \
--cc=x86@kernel.org \
--cc=yechuan@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.