From: kernel test robot <lkp@intel.com>
To: Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 1/3] btrfs: introduce the device layout aware per-profile available space
Date: Wed, 4 Feb 2026 07:49:13 +0800 [thread overview]
Message-ID: <202602040700.ald285sK-lkp@intel.com> (raw)
In-Reply-To: <eb573bac21a16092d8e9f64533c6b0d6ed6b16a4.1770087101.git.wqu@suse.com>
Hi Qu,
kernel test robot noticed the following build errors:
[auto build test ERROR on kdave/for-next]
[also build test ERROR on linus/master v6.19-rc8 next-20260203]
[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/Qu-Wenruo/btrfs-introduce-the-device-layout-aware-per-profile-available-space/20260203-110526
base: https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-next
patch link: https://lore.kernel.org/r/eb573bac21a16092d8e9f64533c6b0d6ed6b16a4.1770087101.git.wqu%40suse.com
patch subject: [PATCH 1/3] btrfs: introduce the device layout aware per-profile available space
config: powerpc-randconfig-002-20260204 (https://download.01.org/0day-ci/archive/20260204/202602040700.ald285sK-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 14.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260204/202602040700.ald285sK-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/202602040700.ald285sK-lkp@intel.com/
All errors (new ones prefixed by >>):
powerpc-linux-ld: fs/btrfs/volumes.o: in function `alloc_virtual_chunk':
>> volumes.c:(.text+0x2648): undefined reference to `__udivdi3'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-02-03 23:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 3:01 [PATCH 0/3] btrfs: unbalanced disks aware per-profile available space estimation Qu Wenruo
2026-02-03 3:01 ` [PATCH 1/3] btrfs: introduce the device layout aware per-profile available space Qu Wenruo
2026-02-03 12:56 ` Filipe Manana
2026-02-03 20:52 ` Qu Wenruo
2026-02-03 21:47 ` Filipe Manana
2026-02-03 23:49 ` kernel test robot [this message]
2026-02-03 3:01 ` [PATCH 2/3] btrfs: update per-profile available estimation Qu Wenruo
2026-02-03 3:01 ` [PATCH 3/3] btrfs: use per-profile available space in calc_available_free_space() Qu Wenruo
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=202602040700.ald285sK-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=wqu@suse.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