From: kernel test robot <lkp@intel.com>
To: Ahmed Zaki <ahmed.zaki@intel.com>, netdev@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
intel-wired-lan@lists.osuosl.org, andrew+netdev@lunn.ch,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
davem@davemloft.net, michael.chan@broadcom.com,
tariqt@nvidia.com, anthony.l.nguyen@intel.com,
przemyslaw.kitszel@intel.com, jdamato@fastly.com,
shayd@nvidia.com, akpm@linux-foundation.org,
Ahmed Zaki <ahmed.zaki@intel.com>
Subject: Re: [PATCH net-next v3 1/6] net: move ARFS rmap management to core
Date: Sat, 4 Jan 2025 13:13:31 +0800 [thread overview]
Message-ID: <202501041245.SDb1oN01-lkp@intel.com> (raw)
In-Reply-To: <20250104004314.208259-2-ahmed.zaki@intel.com>
Hi Ahmed,
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/Ahmed-Zaki/net-move-ARFS-rmap-management-to-core/20250104-084501
base: net-next/main
patch link: https://lore.kernel.org/r/20250104004314.208259-2-ahmed.zaki%40intel.com
patch subject: [PATCH net-next v3 1/6] net: move ARFS rmap management to core
config: arm64-randconfig-002-20250104 (https://download.01.org/0day-ci/archive/20250104/202501041245.SDb1oN01-lkp@intel.com/config)
compiler: clang version 16.0.6 (https://github.com/llvm/llvm-project 7cbf1a2591520c2491aa35339f227775f4d3adf6)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250104/202501041245.SDb1oN01-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/202501041245.SDb1oN01-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/net/ethernet/amazon/ena/ena_netdev.c:165:46: error: too few arguments to function call, expected 2, have 1
return netif_enable_cpu_rmap(adapter->netdev);
~~~~~~~~~~~~~~~~~~~~~ ^
include/linux/netdevice.h:2769:5: note: 'netif_enable_cpu_rmap' declared here
int netif_enable_cpu_rmap(struct net_device *dev, unsigned int num_irqs);
^
1 error generated.
vim +165 drivers/net/ethernet/amazon/ena/ena_netdev.c
161
162 static int ena_init_rx_cpu_rmap(struct ena_adapter *adapter)
163 {
164 #ifdef CONFIG_RFS_ACCEL
> 165 return netif_enable_cpu_rmap(adapter->netdev);
166 #else
167 return 0;
168 #endif /* CONFIG_RFS_ACCEL */
169 }
170
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-01-04 5:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-04 0:43 [PATCH net-next v3 0/6] net: napi: add CPU affinity to napi->config Ahmed Zaki
2025-01-04 0:43 ` [PATCH net-next v3 1/6] net: move ARFS rmap management to core Ahmed Zaki
2025-01-04 5:13 ` kernel test robot [this message]
2025-01-04 12:20 ` kernel test robot
2025-01-04 13:02 ` kernel test robot
2025-01-04 0:43 ` [PATCH net-next v3 2/6] net: napi: add internal ARFS rmap management Ahmed Zaki
2025-01-04 0:43 ` [PATCH net-next v3 3/6] net: napi: add CPU affinity to napi_config Ahmed Zaki
2025-01-06 11:42 ` [Intel-wired-lan] " Dan Carpenter
2025-01-04 0:43 ` [PATCH net-next v3 4/6] bnxt: use napi's irq affinity Ahmed Zaki
2025-01-05 6:42 ` Kalesh Anakkur Purayil
2025-01-04 0:43 ` [PATCH net-next v3 5/6] ice: " Ahmed Zaki
2025-01-04 0:43 ` [PATCH net-next v3 6/6] idpf: " Ahmed Zaki
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=202501041245.SDb1oN01-lkp@intel.com \
--to=lkp@intel.com \
--cc=ahmed.zaki@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jdamato@fastly.com \
--cc=kuba@kernel.org \
--cc=llvm@lists.linux.dev \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=shayd@nvidia.com \
--cc=tariqt@nvidia.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).