From: kernel test robot <lkp@intel.com>
To: Greg Ungerer <gerg@linux-m68k.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-m68k@lists.linux-m68k.org,
uclinux-dev@uclinux.org
Subject: [gerg-m68knommu:dt 7/14] arch/m68k/coldfire/intc.c:173:34: error: 'MCFINT_VECBASE' undeclared; did you mean 'MCFINTC2_VECBASE'?
Date: Tue, 07 Apr 2026 12:03:07 +0800 [thread overview]
Message-ID: <202604070242.CarJBiCS-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git dt
head: 96bd1f7e74e2461c1e906031ed49b9dcf3c28296
commit: 64fbd72ed3aeb34a625ac7bb9f4fd37eb2e46a09 [7/14] m68k: coldfire: support devicetree binding for intc controller
config: m68k-randconfig-r052-20260406 (https://download.01.org/0day-ci/archive/20260407/202604070242.CarJBiCS-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 14.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260407/202604070242.CarJBiCS-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/202604070242.CarJBiCS-lkp@intel.com/
All errors (new ones prefixed by >>):
arch/m68k/coldfire/intc.c: In function 'intc_of_init':
>> arch/m68k/coldfire/intc.c:173:34: error: 'MCFINT_VECBASE' undeclared (first use in this function); did you mean 'MCFINTC2_VECBASE'?
173 | const unsigned int num = MCFINT_VECBASE + 64;
| ^~~~~~~~~~~~~~
| MCFINTC2_VECBASE
arch/m68k/coldfire/intc.c:173:34: note: each undeclared identifier is reported only once for each function it appears in
vim +173 arch/m68k/coldfire/intc.c
169
170 static int __init intc_of_init(struct device_node *np,
171 struct device_node *parent)
172 {
> 173 const unsigned int num = MCFINT_VECBASE + 64;
174 struct irq_domain *domain;
175 int irq;
176
177 domain = irq_domain_add_linear(np, num, &intc_irqdomain_ops, NULL);
178
179 for (irq = MCFINT_VECBASE; irq < num; irq++)
180 irq_create_mapping(domain, irq);
181
182 return 0;
183 }
184
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-04-07 4:03 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=202604070242.CarJBiCS-lkp@intel.com \
--to=lkp@intel.com \
--cc=gerg@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=uclinux-dev@uclinux.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 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.