netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Edward Cree <ecree@solarflare.com>,
	linux-net-drivers@solarflare.com, davem@davemloft.net
Cc: kbuild-all@lists.01.org, netdev@vger.kernel.org
Subject: Re: [PATCH v4 net-next 09/16] sfc_ef100: implement ndo_open/close and EVQ probing
Date: Sat, 25 Jul 2020 05:54:52 +0800	[thread overview]
Message-ID: <202007250522.Sj571vEA%lkp@intel.com> (raw)
In-Reply-To: <99361c13-e3d8-2517-5803-f52d279a7c5a@solarflare.com>

[-- Attachment #1: Type: text/plain, Size: 3286 bytes --]

Hi Edward,

I love your patch! Yet something to improve:

[auto build test ERROR on net-next/master]

url:    https://github.com/0day-ci/linux/commits/Edward-Cree/sfc-driver-for-EF100-family-NICs-part-1/20200725-000401
base:   https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git 1b6687e31a2df9fbdb12d25c1d1d372777bf96a8
config: microblaze-randconfig-r021-20200725 (attached as .config)
compiler: microblaze-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=microblaze 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

>> drivers/net/ethernet/sfc/ef100_nic.c:280:16: error: 'ef100_enqueue_skb' undeclared here (not in a function); did you mean 'efx_enqueue_skb_tso'?
     280 |  .tx_enqueue = ef100_enqueue_skb,
         |                ^~~~~~~~~~~~~~~~~
         |                efx_enqueue_skb_tso
>> drivers/net/ethernet/sfc/ef100_nic.c:285:15: error: '__ef100_rx_packet' undeclared here (not in a function)
     285 |  .rx_packet = __ef100_rx_packet,
         |               ^~~~~~~~~~~~~~~~~

vim +280 drivers/net/ethernet/sfc/ef100_nic.c

   247	
   248	/*	NIC level access functions
   249	 */
   250	const struct efx_nic_type ef100_pf_nic_type = {
   251		.revision = EFX_REV_EF100,
   252		.is_vf = false,
   253		.probe = ef100_probe_pf,
   254		.mcdi_max_ver = 2,
   255		.mcdi_request = ef100_mcdi_request,
   256		.mcdi_poll_response = ef100_mcdi_poll_response,
   257		.mcdi_read_response = ef100_mcdi_read_response,
   258		.mcdi_poll_reboot = ef100_mcdi_poll_reboot,
   259		.mcdi_reboot_detected = ef100_mcdi_reboot_detected,
   260		.irq_enable_master = efx_port_dummy_op_void,
   261		.irq_disable_non_ev = efx_port_dummy_op_void,
   262		.push_irq_moderation = efx_channel_dummy_op_void,
   263		.min_interrupt_mode = EFX_INT_MODE_MSIX,
   264		.map_reset_reason = ef100_map_reset_reason,
   265		.map_reset_flags = ef100_map_reset_flags,
   266		.reset = ef100_reset,
   267	
   268		.check_caps = ef100_check_caps,
   269	
   270		.ev_probe = ef100_ev_probe,
   271		.ev_init = ef100_ev_init,
   272		.ev_fini = efx_mcdi_ev_fini,
   273		.ev_remove = efx_mcdi_ev_remove,
   274		.irq_handle_msi = ef100_msi_interrupt,
   275		.ev_process = ef100_ev_process,
   276		.ev_read_ack = ef100_ev_read_ack,
   277		.tx_probe = ef100_tx_probe,
   278		.tx_init = ef100_tx_init,
   279		.tx_write = ef100_tx_write,
 > 280		.tx_enqueue = ef100_enqueue_skb,
   281		.rx_probe = efx_mcdi_rx_probe,
   282		.rx_init = efx_mcdi_rx_init,
   283		.rx_remove = efx_mcdi_rx_remove,
   284		.rx_write = ef100_rx_write,
 > 285		.rx_packet = __ef100_rx_packet,
   286	
   287		/* Per-type bar/size configuration not used on ef100. Location of
   288		 * registers is defined by extended capabilities.
   289		 */
   290		.mem_bar = NULL,
   291		.mem_map_size = NULL,
   292	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 25382 bytes --]

  reply	other threads:[~2020-07-24 22:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-24 15:56 [PATCH v4 net-next 00/16] sfc: driver for EF100 family NICs, part 1 Edward Cree
2020-07-24 15:57 ` [PATCH v4 net-next 01/16] sfc: remove efx_ethtool_nway_reset() Edward Cree
2020-07-24 15:57 ` [PATCH v4 net-next 02/16] sfc_ef100: add EF100 register definitions Edward Cree
2020-07-24 15:57 ` [PATCH v4 net-next 03/16] sfc_ef100: register accesses on EF100 Edward Cree
2020-07-24 15:57 ` [PATCH v4 net-next 04/16] sfc: skeleton EF100 PF driver Edward Cree
2020-07-24 20:32   ` kernel test robot
2020-07-27 10:41     ` Edward Cree
2020-07-24 21:44   ` kernel test robot
2020-07-24 15:58 ` [PATCH v4 net-next 05/16] sfc_ef100: reset-handling stub Edward Cree
2020-07-24 15:58 ` [PATCH v4 net-next 06/16] sfc_ef100: PHY probe stub Edward Cree
2020-07-24 15:58 ` [PATCH v4 net-next 07/16] sfc_ef100: don't call efx_reset_down()/up() on EF100 Edward Cree
2020-07-24 15:58 ` [PATCH v4 net-next 08/16] sfc_ef100: implement MCDI transport Edward Cree
2020-07-24 15:59 ` [PATCH v4 net-next 09/16] sfc_ef100: implement ndo_open/close and EVQ probing Edward Cree
2020-07-24 21:54   ` kernel test robot [this message]
2020-07-24 15:59 ` [PATCH v4 net-next 10/16] sfc_ef100: process events for MCDI completions Edward Cree
2020-07-24 15:59 ` [PATCH v4 net-next 11/16] sfc_ef100: read datapath caps, implement check_caps Edward Cree
2020-07-24 16:00 ` [PATCH v4 net-next 12/16] sfc_ef100: extend ef100_check_caps to cover datapath_caps3 Edward Cree
2020-07-24 16:00 ` [PATCH v4 net-next 13/16] sfc_ef100: actually perform resets Edward Cree
2020-07-24 16:00 ` [PATCH v4 net-next 14/16] sfc_ef100: probe the PHY and configure the MAC Edward Cree
2020-07-24 16:01 ` [PATCH v4 net-next 15/16] sfc_ef100: read device MAC address at probe time Edward Cree
2020-07-24 16:01 ` [PATCH v4 net-next 16/16] sfc_ef100: implement ndo_get_phys_port_{id,name} Edward Cree

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=202007250522.Sj571vEA%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=davem@davemloft.net \
    --cc=ecree@solarflare.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-net-drivers@solarflare.com \
    --cc=netdev@vger.kernel.org \
    /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).