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:cpu-model 3/10] arch/m68k/coldfire/m523x.c:93:13: error: implicit declaration of function 'MCFCIR'; did you mean 'MCF_CIR'?
Date: Thu, 19 Nov 2026 07:08:52 +0100 [thread overview]
Message-ID: <20261119070741.Az2SiBZu-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git cpu-model
head: bdf44b7b88a06b5bfcef4a4a64b9baa63b9a6646
commit: 08bb06f5e742469237cc22d7571e443ff5272187 [3/10] m68knommu: probe CPU identity for ColdFire 523x types
config: m68k-randconfig-2000-20261119 (https://download.01.org/0day-ci/archive/20261119/20261119070741.Az2SiBZu-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 15.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261119/20261119070741.Az2SiBZu-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/20261119070741.Az2SiBZu-lkp@intel.com/
All errors (new ones prefixed by >>):
arch/m68k/coldfire/m523x.c: In function 'm523x_probe_cpu':
>> arch/m68k/coldfire/m523x.c:93:13: error: implicit declaration of function 'MCFCIR'; did you mean 'MCF_CIR'? [-Wimplicit-function-declaration]
93 | if (MCFCIR(v) == MCFCIR_5235)
| ^~~~~~
| MCF_CIR
vim +93 arch/m68k/coldfire/m523x.c
87
88 static void __init m523x_probe_cpu(void)
89 {
90 u16 v;
91
92 v = mcf_read16(MCF_CIR);
> 93 if (MCFCIR(v) == MCFCIR_5235)
94 m68k_cpumodel = "5235";
95 else
96 m68k_cpumodel = "523x";
97 m68k_cpurevision = MCFCIR_PRN(v);
98 }
99
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-11-19 6:09 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=20261119070741.Az2SiBZu-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.