public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Yu Kuai <yukuai@fnnas.com>, song@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, linux-raid@vger.kernel.org,
	linux-kernel@vger.kernel.org, linan122@huawei.com,
	xni@redhat.com
Subject: Re: [PATCH 3/7] md: support to align bio to limits
Date: Sun, 23 Nov 2025 05:20:48 +0800	[thread overview]
Message-ID: <202511230429.aSwW3knO-lkp@intel.com> (raw)
In-Reply-To: <20251121051406.1316884-5-yukuai@fnnas.com>

Hi Yu,

kernel test robot noticed the following build errors:

[auto build test ERROR on linus/master]
[also build test ERROR on v6.18-rc6 next-20251121]
[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#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Yu-Kuai/md-raid5-use-mempool-to-allocate-stripe_request_ctx/20251121-131818
base:   linus/master
patch link:    https://lore.kernel.org/r/20251121051406.1316884-5-yukuai%40fnnas.com
patch subject: [PATCH 3/7] md: support to align bio to limits
config: powerpc-randconfig-002-20251123 (https://download.01.org/0day-ci/archive/20251123/202511230429.aSwW3knO-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251123/202511230429.aSwW3knO-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/202511230429.aSwW3knO-lkp@intel.com/

All errors (new ones prefixed by >>):

   powerpc-linux-ld: drivers/md/md.o: in function `md_submit_bio':
>> md.c:(.text+0xf8c4): undefined reference to `__udivdi3'
>> powerpc-linux-ld: md.c:(.text+0xf914): undefined reference to `__umoddi3'

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

  reply	other threads:[~2025-11-22 21:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-21  5:13 [PATCH 0/7] md: raid5,raid0,raid10: align bio to io_opt Yu Kuai
2025-11-21  5:13 ` [PATCH 1/7] md/raid5: use mempool to allocate stripe_request_ctx Yu Kuai
2025-11-21  5:14 ` [PATCH] md: support to align bio to limits Yu Kuai
2025-11-21  5:19   ` Yu Kuai
2025-11-25  1:37   ` kernel test robot
2025-11-25  8:23   ` kernel test robot
2025-11-21  5:14 ` [PATCH 2/7] md/raid5: make sure max_sectors is not less than io_opt Yu Kuai
2025-11-21  5:14 ` [PATCH 3/7] md: support to align bio to limits Yu Kuai
2025-11-22 21:20   ` kernel test robot [this message]
2025-11-21  5:14 ` [PATCH 4/7] md: add a helper md_config_align_limits() Yu Kuai
2025-11-21  5:14 ` [PATCH 5/7] md/raid5: align bio to io_opt Yu Kuai
2025-11-21  5:14 ` [PATCH 6/7] md/raid10: " Yu Kuai
2025-11-21  5:14 ` [PATCH 7/7] md/raid0: " Yu Kuai
2025-11-21  8:59   ` Paul Menzel

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=202511230429.aSwW3knO-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=linan122@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=song@kernel.org \
    --cc=xni@redhat.com \
    --cc=yukuai@fnnas.com \
    /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