oe-kbuild-all.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [freescale-fslc:6.6-1.0.x-imx 2665/11728] sh4-linux-ld: i2c-flexio.c:undefined reference to `flexio_writel'
Date: Sun, 28 Apr 2024 11:00:15 +0800	[thread overview]
Message-ID: <202404281030.3l91oBsB-lkp@intel.com> (raw)

tree:   https://github.com/Freescale/linux-fslc 6.6-1.0.x-imx
head:   37770f55ac9c4f6cd958eb5544939207eed8478f
commit: 28f7ee66a10609525341c91f1aef06e8548f994f [2665/11728] LF-8343-2: driver: i2c: buses: flexio: rework to use mfd
config: sh-randconfig-001-20240428 (https://download.01.org/0day-ci/archive/20240428/202404281030.3l91oBsB-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240428/202404281030.3l91oBsB-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/202404281030.3l91oBsB-lkp@intel.com/

All errors (new ones prefixed by >>):

   sh4-linux-ld: drivers/i2c/busses/i2c-flexio.o: in function `imx_flexio_i2c_isr':
   i2c-flexio.c:(.text+0x218): undefined reference to `flexio_readl'
>> sh4-linux-ld: i2c-flexio.c:(.text+0x21c): undefined reference to `flexio_writel'
   sh4-linux-ld: i2c-flexio.c:(.text+0x3bc): undefined reference to `flexio_writel'
   sh4-linux-ld: i2c-flexio.c:(.text+0x4c4): undefined reference to `flexio_writel'

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

                 reply	other threads:[~2024-04-28  3:01 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=202404281030.3l91oBsB-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=otavio@ossystems.com.br \
    /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;
as well as URLs for NNTP newsgroup(s).