The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Kirill Tkhai <kirill.tkhai@openvz.org>,
	agk@redhat.com, snitzer@redhat.com, dm-devel@redhat.com,
	song@kernel.org, linux-kernel@vger.kernel.org,
	khorenko@virtuozzo.com
Cc: kbuild-all@lists.01.org
Subject: Re: [PATCH 3/4] dm-qcow2: Introduce driver to create block devices over QCOW2 files
Date: Tue, 29 Mar 2022 07:42:54 +0800	[thread overview]
Message-ID: <202203290708.kbbyhG39-lkp@intel.com> (raw)
In-Reply-To: <164846631540.251310.2398727490395218229.stgit@pro>

Hi Kirill,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on device-mapper-dm/for-next]
[also build test ERROR on song-md/md-next linus/master v5.17 next-20220328]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/intel-lab-lkp/linux/commits/Kirill-Tkhai/dm-Introduce-dm-qcow2-driver-to-attach-QCOW2-files-as-block-device/20220328-192031
base:   https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git for-next
config: m68k-allyesconfig (https://download.01.org/0day-ci/archive/20220329/202203290708.kbbyhG39-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://github.com/intel-lab-lkp/linux/commit/c41a15c11909af3588885a88f6622c36dcc9ca35
        git remote add linux-review https://github.com/intel-lab-lkp/linux
        git fetch --no-tags linux-review Kirill-Tkhai/dm-Introduce-dm-qcow2-driver-to-attach-QCOW2-files-as-block-device/20220328-192031
        git checkout c41a15c11909af3588885a88f6622c36dcc9ca35
        # 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/md/dm-qcow2-target.o: in function `calc_cached_parameters':
   dm-qcow2-target.c:(.text+0x10ee): undefined reference to `__divdi3'
   m68k-linux-ld: drivers/md/dm-qcow2-map.o: in function `qio_subclu_indexes':
   dm-qcow2-map.c:(.text+0x15e): undefined reference to `__udivdi3'
   m68k-linux-ld: drivers/md/dm-qcow2-map.o: in function `calc_refcounters_map':
   dm-qcow2-map.c:(.text+0x2be): undefined reference to `__divdi3'
>> m68k-linux-ld: dm-qcow2-map.c:(.text+0x2e8): undefined reference to `__moddi3'
   m68k-linux-ld: drivers/md/dm-qcow2-map.o: in function `process_embedded_qios':
   dm-qcow2-map.c:(.text+0x38fa): undefined reference to `__divdi3'
   m68k-linux-ld: drivers/md/dm-qcow2-map.o: in function `parse_metadata':
   dm-qcow2-map.c:(.text+0x4d7a): undefined reference to `__divdi3'
>> m68k-linux-ld: dm-qcow2-map.c:(.text+0x4d98): undefined reference to `__divdi3'
   m68k-linux-ld: dm-qcow2-map.c:(.text+0x4e00): undefined reference to `__moddi3'
   m68k-linux-ld: dm-qcow2-map.c:(.text+0x4e26): undefined reference to `__divdi3'
   m68k-linux-ld: drivers/md/dm-qcow2-map.o: in function `relocate_refcount_table':
   dm-qcow2-map.c:(.text+0x52ce): undefined reference to `__udivdi3'
   `.exit.text' referenced in section `.data' of sound/soc/codecs/tlv320adc3xxx.o: defined in discarded section `.exit.text' of sound/soc/codecs/tlv320adc3xxx.o

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

  parent reply	other threads:[~2022-03-28 23:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-28 11:18 [PATCH 0/4] dm: Introduce dm-qcow2 driver to attach QCOW2 files as block device Kirill Tkhai
2022-03-28 11:18 ` [PATCH 1/4] dm: Export dm_complete_request() Kirill Tkhai
2022-03-28 11:18 ` [PATCH 2/4] dm: Process .io_hints for drivers not having underlying devices Kirill Tkhai
2022-03-28 11:18 ` [PATCH 3/4] dm-qcow2: Introduce driver to create block devices over QCOW2 files Kirill Tkhai
2022-03-28 20:03   ` kernel test robot
2022-03-28 23:42   ` kernel test robot [this message]
2022-03-29 10:42   ` [PATCH 3/4 v1.5] " Kirill Tkhai
2022-03-29 13:34   ` [dm-devel] [PATCH 3/4] " Christoph Hellwig
2022-03-29 15:24     ` Kirill Tkhai
2022-03-29 22:30       ` Kirill Tkhai
2022-03-28 11:18 ` [PATCH 4/4] dm-qcow2: Add helper for working with dm-qcow2 devices Kirill Tkhai
2022-03-29 13:08 ` [dm-devel] [PATCH 0/4] dm: Introduce dm-qcow2 driver to attach QCOW2 files as block device Christoph Hellwig
2022-03-29 15:14   ` Kirill Tkhai

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=202203290708.kbbyhG39-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=kbuild-all@lists.01.org \
    --cc=khorenko@virtuozzo.com \
    --cc=kirill.tkhai@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=snitzer@redhat.com \
    --cc=song@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox