From: Jonathan Cameron <jonathan.cameron@huawei.com>
To: kernel test robot <lkp@intel.com>
Cc: Frank Li <Frank.Li@nxp.com>, <oe-kbuild-all@lists.linux.dev>,
"Carlos Song" <carlos.song@nxp.com>,
Adrian Fluturel <fluturel.adrian@gmail.com>,
Andy Shevchenko <andriy.shevchenko@intel.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
<linux-i3c@lists.infradead.org>, <linux-iio@vger.kernel.org>
Subject: Re: [jic23-iio:testing 47/49] drivers/base/regmap/regmap-i3c.c:41: undefined reference to `i3c_device_do_xfers'
Date: Tue, 23 Dec 2025 09:31:42 +0000 [thread overview]
Message-ID: <20251223093142.00007880@huawei.com> (raw)
In-Reply-To: <20251223093037.00003f7a@huawei.com>
On Tue, 23 Dec 2025 09:30:37 +0000
Jonathan Cameron <jonathan.cameron@huawei.com> wrote:
> On Tue, 23 Dec 2025 04:17:12 +0800
> kernel test robot <lkp@intel.com> wrote:
>
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git testing
> > head: 4e44c635ba8c281f74001d47e20bbcb7f516530c
> > commit: 6e5f6bf2e3f036e6d7466d2a3322445729ea3356 [47/49] iio: magnetometer: Add mmc5633 sensor
> > config: sparc64-randconfig-001-20251223 (https://download.01.org/0day-ci/archive/20251223/202512230418.nu3V6Yua-lkp@intel.com/config)
> > compiler: sparc64-linux-gcc (GCC) 8.5.0
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251223/202512230418.nu3V6Yua-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/202512230418.nu3V6Yua-lkp@intel.com/
> >
> > All errors (new ones prefixed by >>):
> >
> > sparc64-linux-ld: drivers/base/regmap/regmap-i3c.o: in function `regmap_i3c_read':
> > >> drivers/base/regmap/regmap-i3c.c:41: undefined reference to `i3c_device_do_xfers'
> > sparc64-linux-ld: drivers/base/regmap/regmap-i3c.o: in function `regmap_i3c_write':
> > drivers/base/regmap/regmap-i3c.c:22: undefined reference to `i3c_device_do_xfers'
> > sparc64-linux-ld: drivers/iio/magnetometer/mmc5633.o: in function `mmc5633_is_support_hdr':
> > >> drivers/iio/magnetometer/mmc5633.c:193: undefined reference to `i3c_device_get_supported_xfer_mode'
> > sparc64-linux-ld: drivers/iio/magnetometer/mmc5633.o: in function `mmc5633_read_measurement':
> > >> drivers/iio/magnetometer/mmc5633.c:230: undefined reference to `i3c_device_do_xfers'
> > >> sparc64-linux-ld: drivers/iio/magnetometer/mmc5633.c:237: undefined reference to `i3c_device_do_xfers'
> > sparc64-linux-ld: drivers/iio/magnetometer/mmc5633.c:251: undefined reference to `i3c_device_do_xfers'
> > >> sparc64-linux-ld: drivers/iio/magnetometer/mmc5633.c:230: undefined reference to `i3c_device_do_xfers'
>
> Seems like we need a stub.
+CC the lists to broaden awareness.
>
> Jonathan
>
>
> >
> > Kconfig warnings: (for reference only)
> > WARNING: unmet direct dependencies detected for CAN_DEV
> > Depends on [n]: NETDEVICES [=n] && CAN [=y]
> > Selected by [y]:
> > - CAN [=y] && NET [=y]
> > WARNING: unmet direct dependencies detected for REGMAP_I3C
> > Depends on [n]: I3C [=n]
> > Selected by [y]:
> > - MMC5633 [=y] && IIO [=y] && (I2C [=y] || I3C [=n])
> >
> >
> > vim +41 drivers/base/regmap/regmap-i3c.c
> >
> > 6445500b43129b Vitor Soares 2019-06-06 24
> > 6445500b43129b Vitor Soares 2019-06-06 25 static int regmap_i3c_read(void *context,
> > 6445500b43129b Vitor Soares 2019-06-06 26 const void *reg, size_t reg_size,
> > 6445500b43129b Vitor Soares 2019-06-06 27 void *val, size_t val_size)
> > 6445500b43129b Vitor Soares 2019-06-06 28 {
> > 6445500b43129b Vitor Soares 2019-06-06 29 struct device *dev = context;
> > 6445500b43129b Vitor Soares 2019-06-06 30 struct i3c_device *i3c = dev_to_i3cdev(dev);
> > 79c3ae7ada0548 Frank Li 2025-10-28 31 struct i3c_xfer xfers[2];
> > 6445500b43129b Vitor Soares 2019-06-06 32
> > 6445500b43129b Vitor Soares 2019-06-06 33 xfers[0].rnw = false;
> > 6445500b43129b Vitor Soares 2019-06-06 34 xfers[0].len = reg_size;
> > 6445500b43129b Vitor Soares 2019-06-06 35 xfers[0].data.out = reg;
> > 6445500b43129b Vitor Soares 2019-06-06 36
> > 6445500b43129b Vitor Soares 2019-06-06 37 xfers[1].rnw = true;
> > 6445500b43129b Vitor Soares 2019-06-06 38 xfers[1].len = val_size;
> > 6445500b43129b Vitor Soares 2019-06-06 39 xfers[1].data.in = val;
> > 6445500b43129b Vitor Soares 2019-06-06 40
> > c2f2b01b74be8b Linus Torvalds 2025-12-08 @41 return i3c_device_do_xfers(i3c, xfers, ARRAY_SIZE(xfers), I3C_SDR);
> > 6445500b43129b Vitor Soares 2019-06-06 42 }
> > 6445500b43129b Vitor Soares 2019-06-06 43
> >
> > :::::: The code at line 41 was first introduced by commit
> > :::::: c2f2b01b74be8b40a2173372bcd770723f87e7b2 Merge tag 'i3c/for-6.19' of git://git.kernel.org/pub/scm/linux/kernel/git/i3c/linux
> >
> > :::::: TO: Linus Torvalds <torvalds@linux-foundation.org>
> > :::::: CC: Linus Torvalds <torvalds@linux-foundation.org>
> >
>
parent reply other threads:[~2025-12-23 9:31 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20251223093037.00003f7a@huawei.com>]
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=20251223093142.00007880@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andriy.shevchenko@intel.com \
--cc=carlos.song@nxp.com \
--cc=fluturel.adrian@gmail.com \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=lkp@intel.com \
--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 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).