Linux M68K Architecture development
 help / color / mirror / Atom feed
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 14/14] arch/m68k/coldfire/intc.c:173:34: error: 'MCFINT_VECBASE' undeclared; did you mean 'MCFINTC2_VECBASE'?
Date: Tue, 19 May 2026 03:56:46 +0800	[thread overview]
Message-ID: <202605190333.6rPEf5r5-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git dt
head:   3173490642db7ab3c9f15b139b19a633a2ac2d5e
commit: 3173490642db7ab3c9f15b139b19a633a2ac2d5e [14/14] m68k: coldfire: enable devicetree use
config: m68k-m5249evb_defconfig (https://download.01.org/0day-ci/archive/20260519/202605190333.6rPEf5r5-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260519/202605190333.6rPEf5r5-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/202605190333.6rPEf5r5-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

7db34a01c2d5eea arch/m68k/coldfire/intc.c               Greg Ungerer 2025-01-26  169  
7db34a01c2d5eea arch/m68k/coldfire/intc.c               Greg Ungerer 2025-01-26  170  static int __init intc_of_init(struct device_node *np,
7db34a01c2d5eea arch/m68k/coldfire/intc.c               Greg Ungerer 2025-01-26  171  			       struct device_node *parent)
7db34a01c2d5eea arch/m68k/coldfire/intc.c               Greg Ungerer 2025-01-26  172  {
7db34a01c2d5eea arch/m68k/coldfire/intc.c               Greg Ungerer 2025-01-26 @173  	const unsigned int num = MCFINT_VECBASE + 64;
7db34a01c2d5eea arch/m68k/coldfire/intc.c               Greg Ungerer 2025-01-26  174  	struct irq_domain *domain;
7db34a01c2d5eea arch/m68k/coldfire/intc.c               Greg Ungerer 2025-01-26  175  	int irq;
7db34a01c2d5eea arch/m68k/coldfire/intc.c               Greg Ungerer 2025-01-26  176  
7db34a01c2d5eea arch/m68k/coldfire/intc.c               Greg Ungerer 2025-01-26  177  	domain = irq_domain_add_linear(np, num, &intc_irqdomain_ops, NULL);
7db34a01c2d5eea arch/m68k/coldfire/intc.c               Greg Ungerer 2025-01-26  178  
7db34a01c2d5eea arch/m68k/coldfire/intc.c               Greg Ungerer 2025-01-26  179  	for (irq = MCFINT_VECBASE; irq < num; irq++)
7db34a01c2d5eea arch/m68k/coldfire/intc.c               Greg Ungerer 2025-01-26  180  		irq_create_mapping(domain, irq);
7db34a01c2d5eea arch/m68k/coldfire/intc.c               Greg Ungerer 2025-01-26  181  
7db34a01c2d5eea arch/m68k/coldfire/intc.c               Greg Ungerer 2025-01-26  182  	return 0;
33a21263bf74177 arch/m68knommu/platform/coldfire/intc.c Greg Ungerer 2009-04-30  183  }
33a21263bf74177 arch/m68knommu/platform/coldfire/intc.c Greg Ungerer 2009-04-30  184  

:::::: The code at line 173 was first introduced by commit
:::::: 7db34a01c2d5eea204f9833f6bd031d24cf0558f m68k: coldfire: support devicetree binding for intc controller

:::::: TO: Greg Ungerer <gerg@linux-m68k.org>
:::::: CC: Greg Ungerer <gerg@kernel.org>

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-05-18 19:57 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=202605190333.6rPEf5r5-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox