From: kernel test robot <lkp@intel.com>
To: Chuang Wang <nashuiliang@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev,
Chuang Wang <nashuiliang@gmail.com>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
Stanislav Fomichev <sdf.kernel@gmail.com>,
Kuniyuki Iwashima <kuniyu@google.com>,
Samiullah Khawaja <skhawaja@google.com>,
Hangbin Liu <liuhangbin@gmail.com>,
Neal Cardwell <ncardwell@google.com>,
Martin KaFai Lau <martin.lau@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v5] net: reduce RFS/ARFS flow updates by checking LLC affinity
Date: Thu, 28 May 2026 18:54:19 +0800 [thread overview]
Message-ID: <202605281822.xLK0Dj87-lkp@intel.com> (raw)
In-Reply-To: <20260525025854.13982-1-nashuiliang@gmail.com>
Hi Chuang,
kernel test robot noticed the following build errors:
[auto build test ERROR on net-next/main]
url: https://github.com/intel-lab-lkp/linux/commits/Chuang-Wang/net-reduce-RFS-ARFS-flow-updates-by-checking-LLC-affinity/20260525-110036
base: net-next/main
patch link: https://lore.kernel.org/r/20260525025854.13982-1-nashuiliang%40gmail.com
patch subject: [PATCH net-next v5] net: reduce RFS/ARFS flow updates by checking LLC affinity
config: sh-sh7763rdp_defconfig (https://download.01.org/0day-ci/archive/20260528/202605281822.xLK0Dj87-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260528/202605281822.xLK0Dj87-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/202605281822.xLK0Dj87-lkp@intel.com/
All errors (new ones prefixed by >>):
sh4-linux-ld: net/ipv4/tcp.o: in function `tcp_splice_read':
>> tcp.c:(.text+0x3e90): undefined reference to `sock_rps_record_flow'
sh4-linux-ld: net/ipv4/tcp.o: in function `tcp_zerocopy_receive':
tcp.c:(.text+0x4cf4): undefined reference to `sock_rps_record_flow'
sh4-linux-ld: net/ipv4/af_inet.o: in function `inet_send_prepare':
>> af_inet.c:(.text+0x538): undefined reference to `sock_rps_record_flow'
sh4-linux-ld: net/ipv4/af_inet.o: in function `inet_recvmsg':
af_inet.c:(.text+0x570): undefined reference to `sock_rps_record_flow'
sh4-linux-ld: net/ipv4/af_inet.o: in function `__inet_accept':
af_inet.c:(.text+0x644): undefined reference to `sock_rps_record_flow'
sh4-linux-ld: net/ipv4/af_inet.o:af_inet.c:(.text+0x2048): more undefined references to `sock_rps_record_flow' follow
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-05-28 10:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 2:58 [PATCH net-next v5] net: reduce RFS/ARFS flow updates by checking LLC affinity Chuang Wang
2026-05-27 1:50 ` Jakub Kicinski
2026-05-27 8:17 ` Xuan Zhuo
2026-05-28 2:16 ` kernel test robot
2026-05-28 10:54 ` kernel test robot [this message]
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=202605281822.xLK0Dj87-lkp@intel.com \
--to=lkp@intel.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=martin.lau@kernel.org \
--cc=nashuiliang@gmail.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=sdf.kernel@gmail.com \
--cc=skhawaja@google.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 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.