From: kernel test robot <lkp@intel.com>
To: Byungchul Park <byungchul@sk.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC 13/19] page_pool: expand scope of is_pp_{netmem,page}() to global
Date: Sat, 10 May 2025 11:29:14 +0800 [thread overview]
Message-ID: <202505101158.3gT6t67h-lkp@intel.com> (raw)
In-Reply-To: <20250509115126.63190-14-byungchul@sk.com>
Hi Byungchul,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:
[auto build test ERROR on fd93b3350b4314eebd8fbf0fea3ca7fe48d777e3]
url: https://github.com/intel-lab-lkp/linux/commits/Byungchul-Park/netmem-rename-struct-net_iov-to-struct-netmem_desc/20250509-195458
base: fd93b3350b4314eebd8fbf0fea3ca7fe48d777e3
patch link: https://lore.kernel.org/r/20250509115126.63190-14-byungchul%40sk.com
patch subject: [RFC 13/19] page_pool: expand scope of is_pp_{netmem,page}() to global
config: x86_64-buildonly-randconfig-001-20250510 (https://download.01.org/0day-ci/archive/20250510/202505101158.3gT6t67h-lkp@intel.com/config)
compiler: clang version 20.1.2 (https://github.com/llvm/llvm-project 58df0ef89dd64126512e4ee27b4ac3fd8ddf6247)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250510/202505101158.3gT6t67h-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/202505101158.3gT6t67h-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: undefined symbol: is_pp_netmem
>>> referenced by skbuff.c:1040 (net/core/skbuff.c:1040)
>>> net/core/skbuff.o:(skb_pp_frag_ref) in archive vmlinux.a
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2025-05-10 3:29 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20250509115126.63190-14-byungchul@sk.com>]
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=202505101158.3gT6t67h-lkp@intel.com \
--to=lkp@intel.com \
--cc=byungchul@sk.com \
--cc=llvm@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox