public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: kernel test robot <lkp@intel.com>
Cc: Liam Beguin <liambeguin@gmail.com>, <kbuild-all@lists.01.org>,
	<linux-kernel@vger.kernel.org>, Peter Rosin <peda@axentia.se>,
	"Andy Shevchenko" <andy.shevchenko@gmail.com>
Subject: Re: [jic23-iio:testing 231/235] iio-test-rescale.c:undefined reference to `kunit_binary_assert_format'
Date: Mon, 28 Feb 2022 10:17:03 +0000	[thread overview]
Message-ID: <20220228101703.00002a76@Huawei.com> (raw)
In-Reply-To: <202202280119.ftKfZpaB-lkp@intel.com>

On Mon, 28 Feb 2022 01:18:31 +0800
kernel test robot <lkp@intel.com> wrote:

> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git testing
> head:   95df41f4ef19f5884269e6c62dc1d128a23c94cb
> commit: 683352565c0396077086ae0bec530d03e6b3c6df [231/235] iio: test: add basic tests for the iio-rescale driver
> config: m68k-randconfig-m031-20220227 (https://download.01.org/0day-ci/archive/20220228/202202280119.ftKfZpaB-lkp@intel.com/config)
> compiler: m68k-linux-gcc (GCC) 11.2.0
> reproduce (this is a W=1 build):
>         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         # https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git/commit/?id=683352565c0396077086ae0bec530d03e6b3c6df
>         git remote add jic23-iio https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git
>         git fetch --no-tags jic23-iio testing
>         git checkout 683352565c0396077086ae0bec530d03e6b3c6df
>         # save the config file to linux build tree
>         mkdir build_dir
>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=m68k SHELL=/bin/bash
> 
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
> 
> All errors (new ones prefixed by >>):
> 
>    m68k-linux-ld: drivers/iio/test/iio-test-rescale.o: in function `iio_rescale_test_offset':
> >> iio-test-rescale.c:(.text+0xaa): undefined reference to `kunit_binary_assert_format'
> >> m68k-linux-ld: iio-test-rescale.c:(.text+0x134): undefined reference to `kunit_binary_str_assert_format'  
>    m68k-linux-ld: drivers/iio/test/iio-test-rescale.o: in function `iio_rescale_test_scale':
>    iio-test-rescale.c:(.text+0x35e): undefined reference to `kunit_binary_assert_format'
>    m68k-linux-ld: iio-test-rescale.c:(.text+0x4a6): undefined reference to `kunit_binary_assert_format'
>    m68k-linux-ld: iio-test-rescale.c:(.text+0x514): undefined reference to `kunit_binary_assert_format'
>    m68k-linux-ld: iio-test-rescale.c:(.text+0x600): undefined reference to `kunit_binary_assert_format'
>    m68k-linux-ld: iio-test-rescale.c:(.text+0x66e): undefined reference to `kunit_binary_assert_format'
>    m68k-linux-ld: drivers/iio/test/iio-test-rescale.o: in function `iio_rescale_test_offset':
> >> iio-test-rescale.c:(.text+0x20): undefined reference to `kunit_kmalloc_array'  
>    m68k-linux-ld: iio-test-rescale.c:(.text+0xfa): undefined reference to `kunit_do_assertion'
>    m68k-linux-ld: drivers/iio/test/iio-test-rescale.o: in function `iio_rescale_test_scale':
>    iio-test-rescale.c:(.text+0x2e0): undefined reference to `kunit_kmalloc_array'
>    m68k-linux-ld: iio-test-rescale.c:(.text+0x3ae): undefined reference to `kunit_do_assertion'
>    m68k-linux-ld: net/core/sock.o: in function `sk_destruct':
>    (.text+0x411a): undefined reference to `__sk_defer_free_flush'

Looks like we need depends on KUNIT=y

I'll make that change an push out again.

Thanks,

Jonathan

> 
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org


      reply	other threads:[~2022-02-28 10:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-27 17:18 [jic23-iio:testing 231/235] iio-test-rescale.c:undefined reference to `kunit_binary_assert_format' kernel test robot
2022-02-28 10:17 ` Jonathan Cameron [this message]

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=20220228101703.00002a76@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=kbuild-all@lists.01.org \
    --cc=liambeguin@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=peda@axentia.se \
    /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