From: kernel test robot <lkp@intel.com>
To: Andreas Hindborg <nmi@metaspace.dk>, Ming Lei <ming.lei@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Matias Bjorling <Matias.Bjorling@wdc.com>,
Hans Holmberg <Hans.Holmberg@wdc.com>,
Jens Axboe <axboe@kernel.dk>, Minwoo Im <minwoo.im.dev@gmail.com>,
Aravind Ramesh <Aravind.Ramesh@wdc.com>,
gost.dev@samsung.com, linux-block@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
Damien Le Moal <dlemoal@kernel.org>,
Andreas Hindborg <a.hindborg@samsung.com>
Subject: Re: [PATCH v5 5/5] ublk: enable zoned storage support
Date: Wed, 5 Jul 2023 06:15:56 +0800 [thread overview]
Message-ID: <202307050609.y0CCTok8-lkp@intel.com> (raw)
In-Reply-To: <20230704165209.514591-6-nmi@metaspace.dk>
Hi Andreas,
kernel test robot noticed the following build errors:
[auto build test ERROR on 3261ea42710e9665c9151006049411bd23b5411f]
url: https://github.com/intel-lab-lkp/linux/commits/Andreas-Hindborg/ublk-add-opcode-offsets-for-DRV_IN-DRV_OUT/20230705-005338
base: 3261ea42710e9665c9151006049411bd23b5411f
patch link: https://lore.kernel.org/r/20230704165209.514591-6-nmi%40metaspace.dk
patch subject: [PATCH v5 5/5] ublk: enable zoned storage support
config: powerpc-allmodconfig (https://download.01.org/0day-ci/archive/20230705/202307050609.y0CCTok8-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230705/202307050609.y0CCTok8-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/202307050609.y0CCTok8-lkp@intel.com/
All errors (new ones prefixed by >>, old ones prefixed by <<):
>> ERROR: modpost: "__udivdi3" [drivers/block/ublk_drv.ko] undefined!
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-07-04 22:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 16:52 [PATCH v5 0/5] ublk: enable zoned storage support Andreas Hindborg
2023-07-04 16:52 ` [PATCH v5 1/5] ublk: add opcode offsets for DRV_IN/DRV_OUT Andreas Hindborg
2023-07-04 23:33 ` Damien Le Moal
2023-07-04 16:52 ` [PATCH v5 2/5] ublk: move types to shared header file Andreas Hindborg
2023-07-04 23:42 ` Damien Le Moal
2023-07-05 10:50 ` Andreas Hindborg (Samsung)
2023-07-04 16:52 ` [PATCH v5 3/5] ublk: rename driver files to prepare for multiple translation units Andreas Hindborg
2023-07-04 23:43 ` Damien Le Moal
2023-07-04 16:52 ` [PATCH v5 4/5] ublk: add helper to check if device supports user copy Andreas Hindborg
2023-07-04 23:43 ` Damien Le Moal
2023-07-04 16:52 ` [PATCH v5 5/5] ublk: enable zoned storage support Andreas Hindborg
2023-07-04 22:15 ` kernel test robot [this message]
2023-07-05 0:11 ` kernel test robot
2023-07-05 1:00 ` Damien Le Moal
2023-07-05 8:29 ` Andreas Hindborg (Samsung)
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=202307050609.y0CCTok8-lkp@intel.com \
--to=lkp@intel.com \
--cc=Aravind.Ramesh@wdc.com \
--cc=Hans.Holmberg@wdc.com \
--cc=Matias.Bjorling@wdc.com \
--cc=a.hindborg@samsung.com \
--cc=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=gost.dev@samsung.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=minwoo.im.dev@gmail.com \
--cc=nmi@metaspace.dk \
--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.