From: kernel test robot <lkp@intel.com>
To: Greg Ungerer <gerg@linux-m68k.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>
Subject: arch/m68k/coldfire/m523x.c:82:20: error: implicit declaration of function 'read8'; did you mean 'readb'?
Date: Sat, 04 Jul 2026 05:14:34 +0800 [thread overview]
Message-ID: <202607040536.BiSGmESw-lkp@intel.com> (raw)
Hi Greg,
FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: d2c9a99135da931377240942d44f3dea104cedb8
commit: e1f3a00670d13d1ed901125026c1f65394e670a5 m68k: coldfire: use ColdFire specifc IO access in SoC code
date: 4 weeks ago
config: m68k-randconfig-r122-20260704 (https://download.01.org/0day-ci/archive/20260704/202607040536.BiSGmESw-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 15.2.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260704/202607040536.BiSGmESw-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
| Fixes: e1f3a00670d1 ("m68k: coldfire: use ColdFire specifc IO access in SoC code")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202607040536.BiSGmESw-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from arch/m68k/include/asm/io.h:6,
from include/linux/io.h:12,
from arch/m68k/coldfire/m523x.c:20:
arch/m68k/coldfire/m523x.c: In function 'm523x_fec_init':
>> arch/m68k/coldfire/m523x.c:82:20: error: implicit declaration of function 'read8'; did you mean 'readb'? [-Wimplicit-function-declaration]
82 | mcf_write8(read8(MCFGPIO_PAR_FECI2C) | 0xf0, MCFGPIO_PAR_FECI2C);
| ^~~~~
arch/m68k/include/asm/io_no.h:23:75: note: in definition of macro '__raw_writeb'
23 | #define __raw_writeb(b, addr) (void)((*(__force volatile u8 *) (addr)) = (b))
| ^
arch/m68k/coldfire/m523x.c:82:9: note: in expansion of macro 'mcf_write8'
82 | mcf_write8(read8(MCFGPIO_PAR_FECI2C) | 0xf0, MCFGPIO_PAR_FECI2C);
| ^~~~~~~~~~
vim +82 arch/m68k/coldfire/m523x.c
78
79 static void __init m523x_fec_init(void)
80 {
81 /* Set multi-function pins to ethernet use */
> 82 mcf_write8(read8(MCFGPIO_PAR_FECI2C) | 0xf0, MCFGPIO_PAR_FECI2C);
83 }
84
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-03 21:14 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=202607040536.BiSGmESw-lkp@intel.com \
--to=lkp@intel.com \
--cc=arnd@arndb.de \
--cc=gerg@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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.