From: kernel test robot <lkp@intel.com>
To: Dmitry Dunaev <dunaev@tecon.ru>
Cc: oe-kbuild-all@lists.linux.dev, dunaich@mail.ru,
Dmitry Dunaev <dunaev@tecon.ru>,
Thomas Gleixner <tglx@linutronix.de>,
Marc Zyngier <maz@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: Re: [PATCH] irqchip/riscv-intc: Mark INTC nodes for secondary CPUs as initialized.
Date: Wed, 27 Sep 2023 04:44:26 +0800 [thread overview]
Message-ID: <202309270417.HR9Q4rJN-lkp@intel.com> (raw)
In-Reply-To: <20230926102801.1591126-1-dunaev@tecon.ru>
Hi Dmitry,
kernel test robot noticed the following build errors:
[auto build test ERROR on tip/irq/core]
[also build test ERROR on linus/master v6.6-rc3 next-20230926]
[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/Dmitry-Dunaev/irqchip-riscv-intc-Mark-INTC-nodes-for-secondary-CPUs-as-initialized/20230926-183500
base: tip/irq/core
patch link: https://lore.kernel.org/r/20230926102801.1591126-1-dunaev%40tecon.ru
patch subject: [PATCH] irqchip/riscv-intc: Mark INTC nodes for secondary CPUs as initialized.
config: riscv-randconfig-001-20230926 (https://download.01.org/0day-ci/archive/20230927/202309270417.HR9Q4rJN-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230927/202309270417.HR9Q4rJN-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/202309270417.HR9Q4rJN-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/irqchip/irq-riscv-intc.c: In function 'riscv_intc_acpi_init':
>> drivers/irqchip/irq-riscv-intc.c:185:58: error: 'node' undeclared (first use in this function)
185 | fwnode_dev_initialized(of_node_to_fwnode(node), true);
| ^~~~
drivers/irqchip/irq-riscv-intc.c:185:58: note: each undeclared identifier is reported only once for each function it appears in
vim +/node +185 drivers/irqchip/irq-riscv-intc.c
169
170 static int __init riscv_intc_acpi_init(union acpi_subtable_headers *header,
171 const unsigned long end)
172 {
173 struct fwnode_handle *fn;
174 struct acpi_madt_rintc *rintc;
175
176 rintc = (struct acpi_madt_rintc *)header;
177
178 /*
179 * The ACPI MADT will have one INTC for each CPU (or HART)
180 * so riscv_intc_acpi_init() function will be called once
181 * for each INTC. We only do INTC initialization
182 * for the INTC belonging to the boot CPU (or boot HART).
183 */
184 if (riscv_hartid_to_cpuid(rintc->hart_id) != smp_processor_id()) {
> 185 fwnode_dev_initialized(of_node_to_fwnode(node), true);
186 return 0;
187 }
188
189 fn = irq_domain_alloc_named_fwnode("RISCV-INTC");
190 if (!fn) {
191 pr_err("unable to allocate INTC FW node\n");
192 return -ENOMEM;
193 }
194
195 return riscv_intc_init_common(fn);
196 }
197
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2023-09-26 20:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 10:28 [PATCH] irqchip/riscv-intc: Mark INTC nodes for secondary CPUs as initialized Dmitry Dunaev
2023-09-26 10:36 ` Anup Patel
2023-10-04 10:18 ` Marc Zyngier
2023-10-04 14:59 ` Anup Patel
2023-10-04 15:32 ` Marc Zyngier
2023-10-04 16:08 ` Anup Patel
2023-09-26 20:44 ` 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=202309270417.HR9Q4rJN-lkp@intel.com \
--to=lkp@intel.com \
--cc=aou@eecs.berkeley.edu \
--cc=dunaev@tecon.ru \
--cc=dunaich@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=maz@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=tglx@linutronix.de \
/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