From: kernel test robot <lkp@intel.com>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
David Wei <dw@davidwei.uk>
Subject: [cilium:pr/netkit-iouring19 570/583] drivers/net/ethernet/mellanox/mlx5/core/en_main.c:5617:7: error: call to undeclared function 'netif_rxq_has_unreadable_mp'; ISO C99 and later do not support implicit function declarations
Date: Fri, 20 Mar 2026 22:24:12 +0800 [thread overview]
Message-ID: <202603202209.dNMkb930-lkp@intel.com> (raw)
tree: https://github.com/cilium/linux.git pr/netkit-iouring19
head: 263b05479cf2219b9610925d32a127cb5adde246
commit: 8b33e9b1c0bee6f058cbe6cf57915e49e58baa9d [570/583] net: Implement netdev_nl_queue_create_doit
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20260320/202603202209.dNMkb930-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260320/202603202209.dNMkb930-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/202603202209.dNMkb930-lkp@intel.com/
Note: the cilium/pr/netkit-iouring19 HEAD 263b05479cf2219b9610925d32a127cb5adde246 builds fine.
It only hurts bisectability.
All errors (new ones prefixed by >>):
>> drivers/net/ethernet/mellanox/mlx5/core/en_main.c:5617:7: error: call to undeclared function 'netif_rxq_has_unreadable_mp'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
5617 | if (!netif_rxq_has_unreadable_mp(dev, queue_index))
| ^
1 error generated.
vim +/netif_rxq_has_unreadable_mp +5617 drivers/net/ethernet/mellanox/mlx5/core/en_main.c
0fa8c93357601c Dragos Tatulea 2026-02-23 5609
df5135fced85bf Dragos Tatulea 2026-02-23 5610 static bool mlx5e_queue_validate_page_size(struct net_device *dev,
df5135fced85bf Dragos Tatulea 2026-02-23 5611 struct netdev_queue_config *qcfg,
df5135fced85bf Dragos Tatulea 2026-02-23 5612 int queue_index)
df5135fced85bf Dragos Tatulea 2026-02-23 5613 {
df5135fced85bf Dragos Tatulea 2026-02-23 5614 if (qcfg->rx_page_size == PAGE_SIZE)
df5135fced85bf Dragos Tatulea 2026-02-23 5615 return true;
df5135fced85bf Dragos Tatulea 2026-02-23 5616
df5135fced85bf Dragos Tatulea 2026-02-23 @5617 if (!netif_rxq_has_unreadable_mp(dev, queue_index))
df5135fced85bf Dragos Tatulea 2026-02-23 5618 return false;
df5135fced85bf Dragos Tatulea 2026-02-23 5619
df5135fced85bf Dragos Tatulea 2026-02-23 5620 return true;
df5135fced85bf Dragos Tatulea 2026-02-23 5621 }
df5135fced85bf Dragos Tatulea 2026-02-23 5622
:::::: The code at line 5617 was first introduced by commit
:::::: df5135fced85bf3c3dfe174f1cf853cdf39312e5 net/mlx5e: SHAMPO, Allow high order pages in zerocopy mode
:::::: TO: Dragos Tatulea <dtatulea@nvidia.com>
:::::: CC: Paolo Abeni <pabeni@redhat.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-20 14:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202603202209.dNMkb930-lkp@intel.com \
--to=lkp@intel.com \
--cc=daniel@iogearbox.net \
--cc=dw@davidwei.uk \
--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