From: kernel test robot <lkp@intel.com>
To: Heng Qi <hengqi@linux.alibaba.com>,
netdev@vger.kernel.org,
virtualization@lists.linux-foundation.org
Cc: oe-kbuild-all@lists.linux.dev, jasowang@redhat.com,
mst@redhat.com, pabeni@redhat.com, kuba@kernel.org,
yinjun.zhang@corigine.com, edumazet@google.com,
davem@davemloft.net, hawk@kernel.org, john.fastabend@gmail.com,
ast@kernel.org, horms@kernel.org, xuanzhuo@linux.alibaba.com
Subject: Re: [PATCH net-next v7 4/4] virtio-net: support rx netdim
Date: Sat, 9 Dec 2023 11:22:11 +0800 [thread overview]
Message-ID: <202312091132.7eR6Cbs9-lkp@intel.com> (raw)
In-Reply-To: <9be20d1e86bea91b373f28401a96401b640ef4d1.1701929854.git.hengqi@linux.alibaba.com>
Hi Heng,
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/Heng-Qi/virtio-net-returns-whether-napi-is-complete/20231207-143044
base: net-next/main
patch link: https://lore.kernel.org/r/9be20d1e86bea91b373f28401a96401b640ef4d1.1701929854.git.hengqi%40linux.alibaba.com
patch subject: [PATCH net-next v7 4/4] virtio-net: support rx netdim
config: nios2-randconfig-r064-20231209 (https://download.01.org/0day-ci/archive/20231209/202312091132.7eR6Cbs9-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231209/202312091132.7eR6Cbs9-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/202312091132.7eR6Cbs9-lkp@intel.com/
All errors (new ones prefixed by >>):
nios2-linux-ld: drivers/net/virtio_net.o: in function `virtnet_rx_dim_work':
virtio_net.c:(.text+0x21dc): undefined reference to `net_dim_get_rx_moderation'
>> virtio_net.c:(.text+0x21dc): relocation truncated to fit: R_NIOS2_CALL26 against `net_dim_get_rx_moderation'
nios2-linux-ld: drivers/net/virtio_net.o: in function `virtnet_poll':
virtio_net.c:(.text+0x97bc): undefined reference to `net_dim'
>> virtio_net.c:(.text+0x97bc): relocation truncated to fit: R_NIOS2_CALL26 against `net_dim'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-12-09 3:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 6:29 [PATCH net-next v7 0/4] virtio-net: support dynamic coalescing moderation Heng Qi
2023-12-07 6:29 ` [PATCH net-next v7 1/4] virtio-net: returns whether napi is complete Heng Qi
2023-12-07 6:29 ` [PATCH net-next v7 2/4] virtio-net: separate rx/tx coalescing moderation cmds Heng Qi
2023-12-07 6:29 ` [PATCH net-next v7 3/4] virtio-net: extract virtqueue coalescig cmd for reuse Heng Qi
2023-12-07 6:29 ` [PATCH net-next v7 4/4] virtio-net: support rx netdim Heng Qi
2023-12-09 3:22 ` kernel test robot [this message]
2023-12-09 10:27 ` Michael S. Tsirkin
2023-12-11 3:56 ` Heng Qi
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=202312091132.7eR6Cbs9-lkp@intel.com \
--to=lkp@intel.com \
--cc=ast@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=hengqi@linux.alibaba.com \
--cc=horms@kernel.org \
--cc=jasowang@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xuanzhuo@linux.alibaba.com \
--cc=yinjun.zhang@corigine.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;
as well as URLs for NNTP newsgroup(s).